Power Automate: call volume quota

Why?

A lot of companies moving to the cloud think that the cloud provider will make everything possible because “Hey!, I’m paying for it right?!“. Even though Microsoft is providing us with a lot, I want to share some considerations regarding your Power Automate Flows 🛠

What?

In this post some aspects to be aware of on Power Platform connectors in Power Automate Flows.

How?

I’m going to share my tips & tricks based on a very cool example: the Microsoft Teams Connector = https://docs.microsoft.com/en-us/connectors/teams/

Microsoft Teams Connector

A useful link with all available Connectors including filtering options:
https://docs.microsoft.com/en-us/connectors/connector-reference/

1) The first aspect to check is the Release Status of the connector. Notice the (Preview) suffix added to the end: you may have guessed that these connectors should be considered “Not Production Ready”. These preview connectors will be visible in any tenant and are not te be mistaken with the preview connectors that will only be visible if you have joined a targeted release program. Knowing this status should give you an indication to do some good expectation management with your users 😉.

2) The second aspect is to check on Known issues and limitations so you can consider these in advance. The Microsoft Teams Connector for example has a message size limit for the Post a message action which could result in the failed error of “Request Entity too large“.

3) The magical third aspect are Throttling limits. To ensure their services some connectors can handle a limit amount of calls within a certain period of time. The Microsoft Teams Connector for example can handle (at the moment) 300 Non-Get requests per connection per 3600 seconds. Should you exceed this limit like posting a message to 400 users within one hour, it could result in the failed error of “Out of call volume quota“.

{
  "statusCode": 403,
  "message": "Out of call volume quota. Quota will be replenished in 00:10:00."
}

TIP: When working with an Apply to each loop, you could add a delay to your loop so you can stay within the limit. 💡

Throttling limits also apply on Power Apps if Connector available there. (forgive me for promoting this idea to increase a throttling limit on the Office 365 Outlook Connector: https://powerusers.microsoft.com/t5/Power-Apps-Ideas/Remove-or-extend-the-25-emails-limit-for-GetEmails-function/idc-p/390846 😇)

4) And off course last but not least: do not forget to check the Tier or Class to see if it is a Standard or Premium Connector to fit your licensing options. Remember:

You can only pick two!

better automation –> better improvements
versus
low-budget automation –> low-budget improvements 😎

Leave a comment