What can cause the trigger for a Power Automate Flow to stop firing?
When the AAD account that owns a Power Automate flow (or Cloudflow, or whatever the name is by the time you read this....) is disabled it sometimes causes the trigger for the flow to stop working, even if you've changed the owner of the flow. Helpful, I know.
It looks like this is caused by the trigger being still owned by the disabled user, which you can check by connecting via SQL to your Dataverse environment and running this query:
select * from callbackregistration where ownerid ='THE_ID_OF_THE_DISABLED_USER_HERE'
This will return a list of all the callbackregistration's (aka: Flow triggers) that are still owned by the disabled user. The fix that we found for this is to, for each flow:
- Stop the flow - it has to be stopped to be able to delete the trigger
- Delete the trigger
- Restart the flow
The trigger will get re-created when the flow is restarted.
The easiest way to delete the trigger is to create a flow and plug each id in that you need to clear, like this:
