You’re offline. This is a read only version of the page.
Announcements
9
I have a question on the capacities that determine how many flows can run concurrently. I am currently building a solution for a client and the requirement is that we stick with the Power Platform itself and dont resort to any other Azure resources. Specifically, we have to check an on premises database that we are accessing data from via Dataverse Virtual Tables. I ran several tests and observed that with an increase of the concurrent flow volume the execution speed of the flow decreases. I would like to understand what the factors are that determine the flow execution speed respectively how we can optimise it.
So specifically I ran a test where the parent flow triggered 1000 childflows which then run a computation. The execution of all the childflows was significantly slower than activating the maximum concurrency limit of 50 which then processes the childflows in batches. I am now trying to understand if there are any license determined capacity limits and if activating a Pay as you Go licensing would speed up the concurrent childflow execution.
I think that describes the limits you hit quiet well: https://learn.microsoft.com/en-us/power-automate/limits-and-config#concurrency-looping-and-debatching-limits
Share
Report
All responses (
Answers (
