Has anyone faced issues with conflicts while trying to update a row in Dataverse using Power Automate? I have faced similar issues with SharePoint files, but its the first time will be doing a large scale Dataverse update flow, hence wanted to know if this is an issue and what the workarounds could be? I tried testing it using multiple users hitting run flow at the same time, but couldn't cause any conflicts. Wondering if Power Automate / Dataverse handles it internally? Any insights appreciated! Thanks!
We have multiple flows where we use have seen concurrent run of the flow by the dataverse user never faced any error.
Power Automate flows generally trigger Dataverse updates through API calls. If two flows trigger nearly simultaneously, Dataverse will manage the updates in the order they arrive.
you can design your flow to capture and handle update errors specifically. If a conflict occurs, you can have your flow log the error, notify a user.
If my response was helpful and addressed your issue, please consider marking it as the solution. Thanks
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
39
Share
Report
All responses (
Answers (
