Handling simultaneous flow triggers: Dataverse record creation

[fs4]

Hello everyone,

Whenever a record is added to my SQL table, I verify whether a record with the same publication date already exists in my publication table in Dataverse. If no such record exists, I create a new entry in this Dataverse table.

The challenge arises when I add multiple records (e.g., 20) to the SQL table simultaneously. This triggers my flow 20 times, and despite the publication date being the same in all 20 records, multiple records (e.g., 4) are created in Dataverse when it should only be one.

Due to simultaneous triggering, I assume there is a lack of awareness that a record is being created through another flow. Is there a way to address this issue?

Thanks!

[rzaneti · Accepted solution]

Hi @fs4 ,

Each of these SQL correspond to a Power Automate flow run, and it can happen simultaneously. As we have, for example, 4 or 5 flow runs at the exact same time, none of them will identify a Dataverse entry from the other flow run, resulting in a 'false' input to your condition.

To solve it, you can turn on the concurrency control (highlighted in green) in the trigger settings tab (highlighted in yellow):

Make sure to set the limit to 1 (highlighted in blue), so Power Automate will not allow more than one simultaneous flow run. A second flow run will start only when the first finishes, and it will be applied for all flow runs corresponding to each of your multiple inserted records in SQL. 

Let me know if it works for you or if you need any additional help!

-------------------------------------------------------------------------
If this is the answer for your question, please mark the post as Solved.
If this answer helps you in any way, please give it a like.

http://digitalmill.net/ 
https://www.linkedin.com/in/raphael-haus-zaneti/ 

[fs4]

@rzaneti 

This solved my issue! Thank you!