parallels update taking a very long time

Then, in parallel branches, send each set through an apply to each action with the REST call inside. In your flow, use filters to break up your array of items into multiple sets-say, one set could have the first 100 items, then the next set could have the next 100, and so on. However, you could try running more than one of them simultaneously. Since a REST call (I assume you're using the send HTTP request action here) can be used for only one item at-a-time, there's no way to speed up this action itself. Hi, you say you've 'put the flow parallelism at maximum,' do you mean you've set the concurrence of an apply to each block to 50, or that you've created hundreds (whatever the maximum is) of parallel branches within the flow? This avoids the use of a conditional inside the loop, which can halve the time to complete. If, for example, you use a condition inside your loop to do one thing to some data and another thing to the rest of the data, perform this data separation outside of the loop using a pair of filter actions, and then run two loops in parallel, each taking the result of one of the filter actions. You will often need to get creative with your filter conditions, but it can significantly reduce the amount of time it takes for your flow to complete.Īnother trick I've found is to break up the loop into multiple loops (again, using the filter action to break up the data). I do this by always using a 'filter' action immediately before the loop, and then feeding the loop with the result of that filter.

While it's not a solution, per se, one way to mitigate the time it takes to complete a 'apply to each' loop is to limit the number of iterations it needs to complete. Yes, the unexplainable slowness of Power Automate flows is something that's rankled me, as well.

Parallels update taking a very long time