Power Platform Community Forum Thread Details

Recently I noticed a change in behavior of the the Service Bus - When a message is received in a queue (peek-lock) trigger.

I have used this trigger to start a cloud flow. And I have set a max concurrency of 10 on this flow:

Now what I see happening after submitting 15 messages is this: 10 flows running, 5 runs waiting:

I am pretty sure I did not see the 5 Waiting instances before. This is a recent change. This is a problem, as the messages for the 5 Waiting flows are already fetched. The running instances of the flow might take so long, that the message locks of the Waiting flows are already expired before the flows start to run.

So it seems I can no longer throttle the amount of running flows while using Service Bus. Is this intentional?

Categories:

Using connectors

Hi JoostWent

Please look into the Limits of automated, scheduled, and instant flows: Limits and config , under "Concurrency, looping, and debatching limits".

Here you will see that if you switch on the concurrency control for your trigger action in your cloud flow - and submit more than the set limit, you get 10 plus the amount of set concurrency control limit as waiting flow runs. Thus if you set the concurrency control limit to 10 flow runs, and submit 20 or more messages in your service bus, you are guaranteed to get 10 running and 10 waiting flow runs. But lets say you submit 30 service bus messages, then there is no guarantee that the last 10 flow runs, will ever result in a flow run. Their recommendation is to turn off concurrency control to ensure that you get your flow runs 🙂

Not ideal at all... We are very dissatisfied with the run queue limitations, both this and the silly 3 hour limit on how long a flow can be in waiting state in the desktop flow run queue.

Best of luck to finding a better solution.

Best regards
Mustafa
RPA-developer
Roskilde municipality, Denmark