Notifications
Announcements
The issue
Hello @Hyldog ,
I'd guess it's a security measure from Microsoft side to protect their APIs - if they just postponed everyone's requests once they reach their limit they could have a very long queue waiting to be processed that could make the API unavailable for other users.
Hi @tom_riha Good guess but I only have 70-something executions and the limit for concurrent executions is 50 so how come it not execute 50 and then 20. So should I make my flow more efficient or do you know how to handle this most effectively?Cheers, Mikkel
it's not related to the limit in the Power Automate flow, based on the error message it's related to the Power BI API. It just can't handle so many requests at the same time. You might try to decrease the concurrency in the loop to give the Power BI API a break, or try to disable it completely.
okay thanks for the elaboration, @tom_riha I will look into ways to decrease the loop as the flow has to run each week.
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.
Michael E. Gernaey 523 Super User 2025 Season 2
Tomac 406 Moderator
abm abm 245 Most Valuable Professional