Trigger Concurrency Queueing

(1) Share

Report

Posted on by IAmIntractable

278

Good Morning Fellow Power Platform Users:

I have searched online for a definitive answer but all of the posts I encountered are old, and none of them address the following:

When trigger concurrency is turned on and the degree of parallelism is set to 1:

1) What is the maximum number of flow instances that will queue?

2) What happens to executions when the queue size is exceeded?

Cite your source for your information if possible.

Thanks

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Michael E. Gernaey

53,414 Super User 2025 Season 2 on at

Like (1)

Report

For the first question here is the answer

Waiting runs

- Not applicable when Concurrency Control is off
- 10 plus the degree of parallelism (1-100) when Concurrency Control is on

This limit describes the highest number of flow runs that can be queued when the flow is at its maximum number of concurrent runs.
Note: Additional triggers that arrive while the waiting runs limit is met might be re-tried by the connector. However, the retry attempts might not succeed if the maximum waiting limit continues to be met for an extended period of time. To ensure all triggers result in flow runs, leave the Concurrency Control setting off in the flow's trigger.

however, if it gets reached (or not) but the flow itself takes a while, they will start getting back different errors from 429 to any other old TCP timeout etc.

It can differ as to what error they get.

Was this reply helpful? Yes No

IAmIntractable 278 on at

Like (0)

Report

Thanks for your response, I was hoping for different information.

So here is my issue:

It is ok to run an unlimited number of simultaneous instances of a flow but when I want to queue them 1 at a time, Microsofts solution it to allow 11 queue slots then disregard all of the other triggered instances?

That is just ridiculous.

Are you sure that the disregarded instances throw an error? Do they appear in the run history? I have found nothing that explicitly states how the instances above the queue size are handled or what specific errors occur. Is it possible to know that the issue was a queue size and set a retry timing to compensate? Or do I have to set the retry count to 1000 to ensure all are completed?

Was this reply helpful? Yes No