Is it possible to wait for a flow run to complete before the next run starts?

[Anonymous]

Hi,

I have a couple of Flows that are triggered when Salesforce records are updated. These records are updated two different ways. Either they are updated manually by a user throughout the day or they are updated in batches in an import process that runs outside of Flow several times a day. When they are updated manually there is no issue with the Flow. However, when the batch process runs, several of the runs error out due to a 429/"rate limit is exceeded" error. I understand why this is happening but I'm trying to come up with a way to prevent it. I need to collect the information from the batch imports so I can't just disregard them. Ideally, I'd like to have Flow wait to start the next run that was triggered until the last run completes. Is there a way to accomplish this? Or any other potential solutions to my problem? I am open to ideas. Thank you!

[v-bacao-msft]

Hi @Anonymous,

It seems that Flow does not support such a feature currently.

It can be considered that when a Flow is executed, it can generate a delivery message as a trigger condition for the next Flow execution. But all of your Flow's triggers are the same, so there is no good way to achieve your needs.

If you want to function that you mentioned to be supported in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

Best Regards,

Barry

[Anonymous]

Thank you for the information @v-bacao-msft!

[LeeHarris · Accepted solution]

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. I havent been able to confirm if this is possible with the Salesforce trigger as I dont have an available connection to set it up.

[Anonymous]

Thank you @LeeHarris! This is exactly what I needed. 

[Earp]

Where is this setting for automatically triggered flow. I have a flow that updates a spreadsheet based on status emails from a server. It will occasionally fail if two emails come in too quickly. I would like to only have it process one at a time.

[PADUser123]

is this still unsolved? can we get at least the status of a flow?

[Ayaz]

Hey,

Where you able to get any resolution? I am facing the same issue.