Have you ever run into this situation? A Power Automate flow that has been working as expected suddenly doesn’t trigger anymore. There are no errors, no failure notifications, and nothing appears in the run history.
This scenario can be particularly confusing in Dynamics 365 and Power Platform, because it leaves you with very few clues on where to start investigating.
If you’re facing this, take a deep breath. The solution might be simpler than you think and hidden in a technical detail called “Callback Registrations.”
What Are “Callback Registrations”?
When you create a flow that triggers on a Dataverse event (like the creation or update of an account), the system creates a record in the background in a table called CallbackRegistration. Think of this record as a “subscription” that tells Dataverse, “Hey, when this specific event happens, please notify my flow so it can start working.”
If this “subscription” becomes invalid for any reason, Dataverse never sends the notification. The result? Your flow never triggers, and the system doesn’t generate an error because, from its perspective, there was no valid “subscription” to notify in the first place.
The Culprit: The Inactive Owner
So, where do things go wrong? Most of the time, the problem lies with the owner of this CallbackRegistration record. Upon investigating the table, we discovered the cause of our problem: the owner was a user who was inactive and unlicensed in the system.
This often happens when an employee who created several flows leaves the company and their account is disabled. Even if you update the flow’s connections, the original “subscription” in Dataverse remains tied to the old user. When that account is deactivated, the subscription becomes invalid, and the trigger fails silently.
Solution 1: The Complete Approach (Reassign Records)
This is the most robust and recommended solution, as it resolves this and other potential issues related to the inactive user.
Navigate to the inactive user’s profile in the Dynamics 365 or Power Platform admin center.
In the command bar, find and select the “Reassign Records” option.
You will be prompted to select a new owner. Choose an active, licensed user (or a team) to receive all records that belonged to the inactive user.
Start the process. You will need to wait a few minutes for the reassignment to complete.
Once finished, all records, including the crucial CallbackRegistrations, will have a new, valid owner. Your flows should start triggering normally again.
Solution 2: The Quick and Targeted Approach
If you don’t want to reassign all of the user’s records, or if you want a faster fix for a specific flow, you can follow these steps:
- Deactivate the Flow: Go to Power Automate, find the problematic flow, and turn it off.
- Delete the Callback Registration: In Dynamics 365, use “Advanced Find” to search the CallbackRegistrations table. Find the record associated with your flow (you can filter by the workflow’s name or ID) and delete it.
- Activate the Flow Again: Return to Power Automate and turn the flow back on. By reactivating the flow, you will force it to create a new CallbackRegistration record, this time owned by you (the user who activated it), who is an active user. This resolves the issue.
Looking Ahead: How to Prevent This Problem
The best way to prevent this headache is to adopt good governance practices:
Use Service Accounts: For flows that are critical to the organization, avoid creating them with individual user accounts. Instead, use a dedicated, properly licensed service account that is not tied to a specific person.
Perform Regular Audits: Periodically check your organization’s most important flows to ensure the owners and connections are active and up-to-date.
The next time a flow decides to “retire” without warning, you’ll know where to look. A quick check of the CallbackRegistration owner can save you hours of frustration and troubleshooting.
