- Knowledge Base
- FAQ
- Microsoft Flow FAQ
Article sections
Summary: | Microsoft Flow FAQ: This article answers the question: Is it possible to wait for a flow run to complete before the next run starts? |
Article Type: | FAQs, How-To |
Related Product(s): | This article relates to the following products:
|
Related Articles(s): | |
Published: |
|
Q: Is it possible to wait for a flow run to complete before the next run starts?
A: If it is a single flow that is handling all of your updates you may be able to make use of the concurrency control on the trigger. Within the settings for the Trigger step of the Flow, it is possible to force the process to wait until the previous run has completed by reducing the concurrency control Degree of Parallelism to 1.
I have had this successfully working recently with the Microsoft Forms trigger. If multiple Form responses are submitted at the same time, they will sit in a waiting state within Flow until they can be processed.
Disclaimer: This approach is provided “as is” and QGate accept no responsibility for loss or corruption of data either directly or indirectly from the use of this approach.
Related Articles
- How does Power BI Licensing work?
- Understanding Date Fields in the Dataverse
- Power BI URL Filtering
- Create Custom Reusable Controls in PowerApps
- Creating Microsoft Dynamics 365 Workflows Tips
- Adding PowerApps to Dynamics 365
- How to: Creating a "Run Once" Daily Trigger using Power Automate
- How-to: Microsoft Dynamics 365 System Backups
- How to check your Microsoft storage use
- Modifying Silently in Dynamics 365