The default behaviour of a Power Automate Flow is to allow multiple instances of the same flow running. But depending on the scenario or implementation, this can be a big problem, for example, a Flow that is triggered when an item is modified and then based on that iterates through a big list of items and updates a field.
Especially when it comes to SharePoint Online, the Flow can be throttled…
Continue Reading michelcarlo’s Article on their blog
https://michelcarlo.wordpress.com/2020/04/27/quick-tip-force-power-automate-flows-to-be-executed-in-a-queue-instead-of-multiple-instances/
Blog Syndicated with michelcarlo’s Permission
More About This Author
-
SharePoint and Office 365 Consultant/Developer always trying to get the best from Microsoft stack (Microsoft 365/Azure/Power Platform and related stuff).
Living in Ireland since 2018, I had previously worked in Brazil as a consultant/developer for Office 365, SharePoint and related technologies for almost 10 years.
Array
Modern Workplace13 April 2024Power Pages and Cloud Flows – Validate user against Dataverse records based on Contact ID
Modern Workplace6 April 2024Download SharePoint library files in Power Pages with JavaScript and Cloud flows – Improved code using jQuery & option to open PDF file in a new tab
Modern Workplace13 March 2024Handle multiple N:N records associate and disassociate requests with JavaScript and Power Pages Web API
Modern Workplace17 February 2024Generic JavaScript Functions to Associate and Disassociate Dataverse records using the Power Pages Web API
