Notifications
Announcements
HI all.
I have 2 queries for Power Platform licensing.
1) Licensing is handled at the tenant level so it doesn't matter whether there is one domain or 8 domains.
2) API calls vary from connector to connector. But basically each time a connector talks to the server with the data that is an API call. The 2,000 API calls in a 24 hour period is for Office 365 "seeded" licenses, not the ones you mention in #1. Microsoft says the vast majority of users never come close to the API limit.
3) That depends on the apps involved. Again in normal usage you'll never come anywhere near the limits.
Thank you so much @Pstork1 for clarifying the doubt.Appreciate it. 🙂
As you mentioned that API calls are the ones which Connectors makes to get data, but As per the blog below it seems all the actions are termed as API calls. Please see the blog which says that "Every card in a flow that gets executed counts as an API call (action). This includes both actions that result in outgoing calls (e.g. calling SharePoint) and actions that don't (e.g. variable setting, delays, etc.). Only completed and failed actions (but not skipped) count toward the limit."
https://support.microsoft.com/en-us/help/4531688/troubleshooting-slow-running-flows
If we consider these all actions as API calls then the limit of 5000 is very less for any complex workflows which involves multiple loops.
Any thoughts by anyone?
Two points to make.
1) Some connectors batch API calls, so its not as simple as one dat card = one API call. Loops in particular tend to batch up calls.
2) The 5,000 limit is for a 24 hour period. And if you exceed the limit your application will continue to work. A message about the excess will be sent to administrators. If you continue to exceed the limits then you may need to buy additional capacity. At this piont after a year I've not had a single client tell me they've exceeded their 5,000 daily API limit.
We were using a workflow which is complex and using lot of actions to process items from a file and add to SharePoint list. It read data in batches and sends email to the users. This flow works fine for around 2500 records. If you run the flow again it slows down and takes huge amount of time to process. It seems that we are hitting the limit.
I want to understand more about "Loops in particular tend to batch up calls." what do you mean by this?
I don't think you are hitting the API limit. But there are also some throughput limits that Microsoft has put in place. I suspect that is what you are running into.
Unfortunately, I don't have any additional details on Batching. Simply that Microsoft says its not a simple 1 action = 1 API call equation.
Is there a way to validate it we are hitting API limits vs throughput limit? How can I check which limit I am hitting?
If you are hitting the API limit then your Global Admins would receive a notification. If you aren't getting that notification then you aren't hitting the API limit. Hitting the throughput throttling will do exactly what you describe. But the only way to know for sure is to open a support ticket with Microsoft.
Thanks for your response. When you say throughput throttling what does that exactly mean?
We tried to run the workflow after specific intervals like after 1 hr. It seems that the throughput limit is reached. Do you have any idea if there is the throughput limit for a specific time( 60 mins, 120 mins) which is trying to block the operation for subsequent runs? Do we need to wait for specific time to execute the workflow to avoid throughput limits?
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
In our never-ending quest to improve we are simplifying the forum hierarchy…
We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
WarrenBelz 739 Most Valuable Professional
Michael E. Gernaey 343 Super User 2025 Season 2
Power Platform 1919 268