Automation slowed down due to plan?

[Garth]

I have an automation that when it runs it normal runs in under 1:30, but we have had to have our Power Automate trigger much more often than normal due to circumstances beyond our control. Here is what is the last few runs look like with the normal run time highlighted:

When I look at one of the runs that did complete that took around seventeen (17) hours, my Do Until looks like this:

However when I look into the tasks within the branch, there are my twenty (21) runs and each one is only taking a couple of seconds.

I am really confused as to why my run is saying it is taking so long, but the individual tasks are running at normal speed. Can anyone explain why this is the case?

Thanks

[Matthy79]

If you consume too many actions you will get throttled. That means that each action will take more time to be send. (That is the time between the actions). Download the report from

https://admin.powerplatform.microsoft.com/resources/downloadreports

and check it.

you should have a look at the actions limits as well. If you share details about your flow, someone can have a look at it and maybe the flow can be redesigned to consume less actions.

[Garth]

Thanks for this, but unfortunately being a Government organisation we do not have access to this link.

My whole automation has only 12 actions, and whilst I could put a lot of the Compose actions together it would make it an absolute bugger to maintain if there are issues or changes.

We have looked up the limits for Free licenses however we cannot understand how it works in a real world scenario. If someone could clarify the numbers into something that is easily explainable that would be great.

[Matthy79]

Someone in your organization has access. Who created your environment you are working in? Who gave you the permissions?

10 actions doesn’t sound a lot. Why are they taking so long? Depending of what actions you are talking about, this flow shouldn’t take more than 2 seconds. Is there a loop included? If yes how many items are you looping? Can you share the current flow setup?

[Garth]

Find the person in my organisation that has the level of access that would have the required access would not be easy.

Yes I do have a Do Until with a few steps in it, and with my current data it runs each iteration 31 times. I know this is where the trouble is and unfortunately cause I am using API calls to an external system that is limiting my "output".

This is the reason I was wondering how to interpret the free licensing restrictions.

[Matthy79]

So you don’t have 10 actions used in your flow each time it runs but about 300. If it runs 50 times a day it will be 15000 requests. Don’t know your license model but this could be the problem. If you go inside a run history that took more time. Is there anything special. Maybe an information at the top about throttling? What action took long?

If you share details to your flow we might reduce the numbers of actions.

[Garth]

Yeah I am getting better acquainted with how the licensing count works. Each step is 1 request some my Do Until is using 11 requests (including the Do Until) and we have to currently run this 32 times, meaning 352 per single run, plus the 35 previous steps for a total of 387 per run. That means if we have a license, this gives us 40,000 requests per floating 24-hour period, meaning we can run the automation 103 times within that period without issue.

Licensing details: Types of Power Automate licenses - Power Platform | Microsoft Learn

Now we are in the process of reducing the number of runs the Do Until has to do which is great, however I don't believe there is much we can do to reduce the number of steps in my Do Until.

For completeness and as requested, I have attached my full flow, now I can appreciate that I could consolidate some of my compose actions on the left, however these are separated to ease troubleshooting and updating, also these only run once.

If someone could offer some tips on streamlining my flow that would be great. Thanks

[Matthy79]

Hello @Garth 

You use a lot of variables. Usually this is not necessary.

Without understanding what the flow does, it is hard to say what to change. I think the reason why you get throttled is clarified. You should create another topic where you work on tuning your flow. I think there is a lot of potential but of course someone has to dig deeper into the business logic.

You can tag me if nobody answers or you get stuck somewhere.

[Garth]

Message posted: https://powerusers.microsoft.com/t5/Using-Flows/Optimising-my-flow-a-few-variables-and-compose-funct...