Use Action Analytics to Avoid Power Automate Throttling

Microsoft recently updated their maker analytics feature to include another report called Action Analytics. Maker analytics was first released back in December 2017. The intent of this feature was to aggregate insights across a flow’s execution history over a period of 28 days. The two reports that were available to us included flow Runs and Errors. Microsoft has recently updated this feature to include Actions.

Why is this significant?

Since the original analytics feature was released, Microsoft has changed their licensing terms which now analyzes flow actions, instead of just runs. Within Microsoft’s documentation it calls out the entitlement provided in each user license. Depending upon how you are entitled to use Power Automate, your number of daily API requests will differ.

What happens if I go over?

If you go over your daily limits, you may experience throttling which will have an impact on how well your flow performs. The Microsoft documentation calls out the following behavior: “In the most common case – exceeding limits will result in delayed execution of subsequent actions – which will slow down the overall execution of your flow run. These delays are proportional to the degree of overages caused by a flow, and they only become apparent when there is egregious violation of limits. “

How can I prevent from going over?

The first thing that a maker can do is evaluate their flow to see if there are excessive APIs being called. This can include unnecessary loops, overusing variables or compose actions. In addition, when possible filter records at source by using Trigger Conditions or by using Odata filters. If you are still encountering issues after performing your flow optimizations, then consider upgrading your User license or acquiring a Flow plan license which will increase your API limit entitlement.