Flow Keeps Running But Never Ends

(0) Share

Report

Posted on by ar87

353

Hi all,

During our final testing the flow started to behave odd and after a thorough research I realized it could be due to reached request limits. However, I would like to confirm that with experts here on forum since MS licensing can be quite confusing.

Here are screenshots of the flow so you can get better understanding of what is going on.

First screenshot shows a flow that is being triggered when an HTTP request is received but the flow just keeps running and never ends.

Second screenshot shows that same flow from earlier today when each flow run was able to successfully finish its run.

The flow stops on the following action:

As I said, I did a research on this issue and found that it has something to do with licensing and license limits.

At the moment, we are still using "Flow Plan 2 Trial", but once the Power Apps application is in production, we are going to purchase Power Apps per app plan for the owner of the flow as well for each user using the app. However, now when this issue emerged, I assume this license won't be sufficient to cover our needs:

a flow that runs once every minute throughout the day and containing approx 45 actions
three other flows with less actions (10-15) and that are less often executed
a lot of CRUD actions on Dataverse (hundreds of CRUD actions in Dataverse tables)

According to the following link: Requests limits and allocations - Power Platform | Microsoft Learn a request (action) in Power Automate is literally everything - from a trigger to a simple compose action.

On the same link under "LICENSED USER REQUEST LIMITS" section I can see different license limitations:

According to the above, I am pretty sure that Power Apps per app plan won't cover our needs. If I am correct, what would you suggest to do, which license(s) should we go for?

Just as a reminder, we want our service account to be the only user to run the flow as it is the case now, so when considering licensing options we can look for a separate license for that user and different licenses for users of the Power Apps application.

EDIT: I was wondering if purchasing more licenses creates a pool to increase that requests limit?

Any advice or help is more than appreciated.

Ty,

Best

Categories:

Licensing

All responses (4)

Answers (0)

ar87 353 on at

Like (0)

Report

Re: Flow Keeps Running But Never Ends

Hi @Matthy79,

That's correct, there are more columns but I intentionally removed them. 🙂 Those I pasted here are related to the env I am running flow in.

Since I have enough privileges, I will search around and try to find where to change the role/licence of the user to get more quantity. Thank you for that advice!

Could you please tell me which licence type you have so I can take it as a direction where to go when deciding what license to buy for our service account?

Thank you.
Matthy79 4,178 Super User 2024 Season 1 on at

Like (1)

Report

Re: Flow Keeps Running But Never Ends

The report is missing some columns. You should see the environment columns as well and the entitled quantity is for each environments.

8000 is the smallest amount. In our tenant I see this quantities for our different users (global admins have to most):

22887 isn't that big amount. You can change the role/licence of the user to get more quantity. Since I am no global admin I don't know exactly where or what to change. But I (for example) have 48000 quantity.

Since MS can't track the amount in real time it is possible to consume more actions but you will be throttled in time.

Also MS announced that in future the consumption won't be environment based but tenant based. I'm not sure if they will really do this because this will cause a lot of troubles for many users.
ar87 353 on at

Like (0)

Report

Re: Flow Keeps Running But Never Ends

Hi @Matthy79,

Thank you for your help. I think the report could help me get exact numbers and based on that decide which license suits my needs.

Could you help me understand why the same user gets entitled 8000 requests two times in same day? Also, why Power Automate Requests are two times 0 and once 22887 requests for the same day? Do you maybe know how to interpret these numbers?

Regarding licenses, now I found new terminology and changes in MS licensing: Types of Power Automate licenses - Power Platform | Microsoft Learn

Both Power Automate per user plan and Power Automate per flow plan are removed from pricelist. However, there is Power Automate premium plan, and it states it contains 40K Power platform limits per 24 hours:

Wish someone could confirm this confusion with MS licensing.

Once again, @Matthy79 thank you for your help.

Best
Matthy79 4,178 Super User 2024 Season 1 on at

Like (1)

Report
Re: Flow Keeps Running But Never Ends

Hello @sdedic,

indeed the licence model of Microsoft is very complicated. Even Microsoft doesn't understand it and if you ask clear questions you won't get the answers you are searching for. I will try to do my best to help with the knowledge I currently have. Hopefully someone else can jump in and adds some useful information.

It is always good to check if you can reduce the actions in flows. Especially when they are triggered so often. Maybe let's have a look at it in a different thread.
Purchasing more licenses won't help, because the flow runs with this specific user and even if you have 100 users with a licence, that will not increase the limit of this one.
Check the current situation for this/all users. Downloadable Reports | Power Platform admin center (microsoft.com)
You will see the limits for each user and also what has been consumed.
You can assign the user a different role on the platform. "Better" roles have more "Entitled Quantity".
A per flow licence could help. In that case you can give specific flows the capability to use more actions. Of course this will cost.
Switch to logic apps. It's the same architecture but with a different licence model. You will pay per use.

Normally you should see an information about that throttle situation within the flow (somewhere on top).

I hope this helps a little.