Dataverse Flow triggering twice on field change - Trigger Condition issue

[priyeshwagh777]

Hi All,

I have a Dataverse trigger Flow which is triggered when a PSA Invoice is Marked as Paid i.e. an out-of-the-box ribbon button on Invoice, the OOB field it changes is Project Invoice Status (msdyn_projectinvoicestatus)


And when I click this button, the Invoice is marked as Paid, but the Flow is triggered twice - 


This is what the Flow trigger looks like - 

We have a Trigger Condition that is fired off a very specific condition i.e. Project Invoice Status = "Invoice Paid"

Also, to back this up, the Audit history looks like it was changed only once.

Any thoughts on why this is the case? The Flows shouldn't be triggered more than once as per the last screenshot where it is changing the field only once (and then the other fields are changed, and not Project Invoice Status)

When trying to work with other fields, it correctly gets triggered only once.

Kindly advise! 🙂

[Haw_Isaac]

We are seeing a very similar phenomenon with our quote entity, albeit only intermittently.

We have a ribbon button that sets the status to submitted and a flow that triggers on that status alone.

We both viewed the audit in application and via XRMToolbox and both showed a single update:

However the flow still triggered twice. Interestingly, the second flow that triggered showed the record had a modified date that was 19 seconds after the first that had triggered:

We still haven't found the root cause, but I am wondering if it might be a double post of the status field updating even though the audit shows a single update.

Please share if you found the cause in your case!

[ManishJain]

Hi @priyeshwagh777 & @Haw_Isaac ,

Can you please check if there are any other plugin or workflow running in the background on change as this happens within milliseconds you wont be able to notice. 

Also as @Haw_Isaac mentioned, can you please put the column and condition in Select Column and Filter rows condition parameter.

Thanks

[priyeshwagh777]

Hi @Haw_Isaac & @ManishJain ,

When I worked with Microsoft Support on this, I learnt that this was being caused due to 2 Callback Registration records being created in Dataverse. This causes the Flows to trigger twice for the same operation.

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/entities/callb...

Now, I don't recollect what was the exact fix but all we did was based on some criteria upon comparing, we just had to delete 1 of the callback registration records in order for the Flow to Run only once as it's supposed to.

If possible, I'll try to get in touch with the support to understand what we'd done back then.

Hope this hint helps! Thanks! 😊

[Naveen_772]

 @ManishJain @Haw_Isaac 

I also noticed the same issue in one of our client env. The cause of the issue was the same. Duplicate callback registrations were present in our env. You can always open a ticket with the Microsoft support team and they will assist you. But to make things clear I am going to explain what they did in our env.

You can always check all callback registrations that are registered for your env and mitigate the issue. 

1. First, you need to identify if there is duplicate callback registration for the same flow. You can use web API to retrieve all the callback registration. This can be a little tricky. You need to compare the "entityname" and "
   filteringattributes" property to identify the duplicate registration.
   •   Link for getting all callback registration :- [org URI]/api/data/v9.0/callbackregistrations

     2. Once you have identified the duplicate call back registration. Grab the "callbackregistrationid" value.

    3. Delete the duplicate callback registration. You can either do it using the web API or a simple flow.

I hope this helps you a little bit. 

Thanks,

Naveen

[priyeshwagh777]

Thanks @Naveen_772 ,

Yes, that's what they did for us as well. Additionally, they also had a specific script to run and identify which of the callback registration to remove.

I'll get in touch with MS Support and see if I can get the exact steps.

Thanks!!

[kevmscotland]

We're encountering a similar issue. We tend to find a deployment creates a duplicate callback registration but we heavily use Power Automate Flow in our system, and continually reviewing the callback registrations for duplicates is a problem we really need resolved.

I'm curious from your time at Microsoft if you have a greater understand of how the Callback Registration works.
We noticed that newer Dataverse connectors seem to use the Flow ID as the name on the callback registration, but this does not apply to Legacy Dataverse callback registrations.

There doesn't appear to be any direct link or relationship you can use to trace a callback registration directly to its Flow, unless I'm missing something else?

[SohoMantis]

I managed to fix by repointing the LA trigger to a different entity.  Saving.  Then repointing back to Account.  Problem solved!

I was facing exactly the same issue with a LogicApp.  Root cause seems to be two Callbackregistration records being created when my triggering Account field was modified.

After trying EVERYTHING (turning LA on and off again, turning off workflows, plug-ins etc, setting concurrency to 1...) I tried the above solution and couldn't believe it when it worked.

My LA is being used to create records in another system so just in case this randomly crops up again I've inserted a Delay step using a random number expression to wait 1-180 seconds -  "rand(1,180)".  If two runs do get kicked off simultaneously  this random delay allows me to add a check if the other run gas already kicked in (by fetching the source record again with a "Get row by id") and checking if it still meets criteria to be processed.

[Toshiki79]

I'm facing the quite similar situation and I'm trying several workarounds before contacting MS to find out the solution for Duplicate callback registrations.

I have a cloud flow that is triggered when a Dataverse for Teams row whose column "Status" is updated from "Draft" to "Submitted" (e.g. User creates the row on "Create" Powerapps Canvas app form with status "Draft", then updates it to "Submitted" on "Confirmation" form). The time between creating the row with "Draft" and updating it to "Submitted" could be short, depending on user's action on Powerapps Canvas app.

If a user waits a bit longer (e.g. 10 seconds) to update the status, the flow runs only once. If it is done in less than 3 seconds on the other hand, the flow somehow runs twice.

Therefore, I only added a timer control onto the "Confirmation" form where users update the record status to "Submitted" so that its update, SubmitForm(), should wait for 15 seconds at least. After implementing it, I haven't faced the problem so far.

[Toshiki79]

It didn't work after all and I've raised a support inquiry with MS support already.

Seems that there're too many inquiries from all over the world  for them to handle and I've still been kept waiting.