Original thread - Flow Performance - What is considered an "action"? - Power Platform Community (microsoft.com)
Hello,
I am having issues with my flows hanging during a do-until loop.
When my flow runs properly it takes about 4-6 minutes to fully execute and the loop normally runs about 130 times. This loop is parsing a text file and converting it to a JSON file.
Many times I am able to get the flow to complete but then after a few successful iterations, it will start hanging and fail, or it will complete but not actually run the proper number of loops. I have set a timeout in the loop as well as a max count. The loop timer appears to not properly trigger and fail the run as I would expect.
Since this has been going on I am also getting an error "Your flow's performance was slow between 1/20/2021 9:29:08 AM and 1/22/2021 3:32:24 PM. It is currently performing normally. Please verify that your flow is optimized and is not using more actions or data than necessary. Learn more" and I am not sure what counts as an action.
Is it a step in the flow?
Is it possible that a step has multiple actions if it is a formulation like substrings or other string manipulations?
Thanks for the help,
-Kurt
@kjordan You can raise ticket with Microsoft and ask them about your requirement. They can suggest you better.
Did my reply help? Please give it a thumbs up.
Did I answer your question? Please mark my post as a solution!
Regards,
Hardesh
I am gathering from this because I need some unlimited plan to process the number of flows that would be logical for my daily needs. This plan does not seem to exist. How could I do the data load required if the system limits my account actions beyond a handful of successful runs? Even if I split the load across multiple flows, it appears that nothing would change the throttling.
@kjordan These are flow limits not connector limit. Connector has additional limit like Do until can run 5000 times.
Thanks
Hardesh
@kjordan 5 good runs means= 5*3200= 16000 executions approx. it may be higher. That is why next execution is slowing down.
Thanks
Hardesh
I feel like the limits are counter-intuitive:
how can executions per 5 minutes be larger than a 24-hour window?
-Kurt
The limit is much larger than that, though.
I am trying to figure out how all of this is computed and what triggers this. I have had 5 good runs, and now a run is hanging for the last 30+ minutes.
Edit: Run just completed in 35 minutes and only iterated through 118 loops, I feel it should have broken in 10 minutes or made it through all the loops, but neither occurred.
@kjordan You do until have 25+ actions and each run counts 25+ execution. So it means you are reaching 130*25= 3250 executions. That is why it is slowing down your loop. It is not stopping here but slowing down. Okay.
Thanks
Hardesh
Right, but both the loop count limit and the set limit are much lower than that. There is no reason that should be a factor. Each run of the flow should only run for 130 iterations or 10 minutes based on my control limits.
This still does not explain how I have runs lasting multiple hours and only complete 40-50 iterations after they "complete."
@kjordan Save you flow copy and turn on this flow and check.