Recently, we observed that one of our flows was getting triggered multiple times in our UAT environment; however, the flow was working properly in our Development environment.
On comparing the flows trigger, we didn’t find any differences.
However, when checking for the callbackregistration record, we observed that for the Dev env, we had the callbackregistration record available.
However, it was missing for our UAT environment.
Turning the flow on and off didn’t create the corresponding callbackregistration record.
Eventually, we deleted the trigger and recreated it in the UAT.
After recreating the trigger, we could see our flow getting triggered only once as expected.
However, we also noticed that the name of the callbackregistration record was not just the GUID, but it also had MTA suffixed to it in our UAT.
daf9fae3-a405-ee11-8f6e-00224817f864:MTA
So may this record was already existing and had an incorrect filter expression, which got fixed when we deleted and created a new trigger.
We also deleted this callbackregistration record, and turned our flow on and off. This created a new callbackregistration record with the same MTA suffixed to it.
So the solution here could be to find the callbackregistration record either with a GUID or with MTA suffixed to it, delete the record found, and turn the flow on and off.
Hope it helps..
Nishant Rana's Weblog 