Troubleshooting tips for flows and CallbackRegistrations

Hi ,

So you are experiencing some issues with Power Automate flows interacting with Dataverse ?

Well this community post will provide you some insights on how to troubleshoot flow triggers and callback registration issues.

Index:

1. What are callback registrations ?
2. Finding callback registrations of a solution aware flow
3. Issues:
   
   1. Flow triggering multiple times
   2. Flow not triggering

What are callback registrations ?

Callbackregistrations in Power Automate flows enable you to subscribe to a specific event or trigger in Dataverse, allowing you to receive notifications when that event occurs.

With callbackregistrations, you don´t need to constantly monitor your data for changes or updates.

Instead, you can sit back and let the system notify you when something important happens.

They are a key part of Power Automate flows, responsible for firing triggers (e.g.: When an account is added or modified)

Finding callbackregistration of a solution aware flow:

Consider the Power Automate flow below:

Since it is solution aware, this means it will appear in the Web API below (for more info read: https://learn.microsoft.com/en-us/power-automate/web-api): 

org.dynamics.crmx.com/api/data/v9.2/workflows

To find the callbackregistrationid of the Power Automate flow in this example, first we need to find its workflowid.

To do that, we can use the previous Web API query, just need to use a filter (and a select to avoid unnecessary information).

/api/data/v9.2/workflows?$select=name,workflowid&$filter=contains(name,'Community Post Flow - When Account is Created')

Once we have the workflowid, if we search for that particular workflowid on org.dynamics.crmx.com/api/data/v9.2/callbackregistrations we expect to see one JSON dictionary where the names matches it.

This callback is what is responsible for triggering the workflow.

Issues: 

Flow triggering multiple times - If your Power Automate flow is triggering more times than you expected one possible reason is that there might be more than 1 callbackregistration for that specific flow. One possible way to mitigate this issue is to search for the workflowid of your Power Automate flow on api/data/v9.2/workflows and check if you get more than 1 match. 

If you do, then this means your flow has more than 1 callback and one way to fix this is to delete one repeated callback. In order to do this:

1. Get one callbackregistration id.

2. In the browser open Developer Tools console and perform this request:

fetch('https:/YourURL.crm.dynamics.com/api/data/v9.0/callbackregistrations()', { method: 'DELETE'})

Flow not triggering - In case your Power Automate solution aware flow is not triggering one possible reason might be that it has no callbackregistration.

To verify this, go to api/data/v9.2/callbackregistrations and search for the workflowid of the flow that is not triggering.

If you do not get any matches, that means there is no callback. In this case, in order to simply recreate the callbackregistration just:

Turn off:

Turn on:

That should create a new callback and the flow should execute once its trigger is met.