Flow waiting for prior run to complete before starting, Looking for simultaneous runs

[jy8402]

Hello, I have a flow that is triggered when a SharePoint item is added. This starts a MS Approval process and completes when finished. When items are added into SharePoint, the flow builds up a backlog of runs that are waiting until the prior run completes. This is an issue as we have hangups as each run is waiting for a full complete cycle of the other runs. 

This does not seem to be a common issue as I have not seen a question on it yet. Is there a setting I need to change? Any feedback is appreciated! 

[Hardesh15]

@jy8402 

As per Microsoft standard free plan, flow trigger can take upto 15 min to take off. With in this 15 min window flow can trigger any time.

If you are using paid license then it will trigger within 2 min or 1 min.

Regards,

Hardesh

[jy8402]

Hello Hardesh, thank you for the reply. The flow is being placed on "waiting" until the prior flow completes its run. There are some flows that are kept on "waiting" for hours. 

[Hardesh15]

@jy8402 

Please share your flow screens.

Thanks

Hardesh

[jy8402]

Hello Hardesh, I have attached the below section of the flow that catches and waits for the approval to occur before other flows start flowing. As you can see in the historical runs, one instance is running for 2+ days while the others are waiting and do not initiate until the prior flow completes. 

Is this something to do with the setting of the Flow or related to the MS Flow component? Appreciate any insight you have! 

[yashkamdar]

Hello Team,

Those flow are waiting to get the responses to the Approvals, until and unless the Approver goes ahead and either Approves or Rejects the Flow will not move forward.

Can you ask the Approver to check in his email box if he has Approval actions pending there and either Approve or Reject this, once he does that the flow will go ahead.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[jy8402 · Accepted solution]

Update on the issue, there is a concurrency setting on the first action trigger module that can be set from 1-50. That setting was placed at 1 and causing the other flows to wait 1 at a time for running! Setting it to 20 has resolved this for me. 

[yashkamdar]

Hello Team,

Awesome, don't know if you can accept your own answer as a solution but if you can then please do ACCEPT it, that way others who might be facing a similar issue will directly be able to read your solution and not have to read the entire history.

[Hardesh15]

@jy8402 

I am glad that you figure out yourself. But in your post you did not mention about this setting at all. This is common problem i have seen. They ask solution but do not share complete information.

Accepting you reply as solution.

Thanks

Hardesh

[cafeolai]

Thank you ,  I had the exact opposite problem where my scheduled flows updating a table would hang one after the other for hours ..  thanks to your post , I found out that there was no limit on concurrency so the table was getting same updates from every flows and lock. I changed the concurrency to 1 and now the updates waits for the previous one to finish which is exactly what I wanted 🙂