Forum Discussion
Refresh button in report
Hi,
Need to add a REFRESH button in the report, tried with Power Automate option, selected workspace, couple of time it worked, later gave the below error.
Alert: Your operation has been throttled. ApiConnection -> Refresh a dataset started experiencing issues at 19:41 ,9/23/2026 UTC
What happened? Looks like your flow's operation is hitting an action limit designed to protect the connector service being called.
I am using free license, is this the issue or what could be the issue or any other options you suggest.
Thanks,
Hi YashikaAgrawal - If the semantic model is on shared capacity, Power BI documents a limit of 8 refresh requests per day for API-triggered refreshes. So a Power Automate button that calls Refresh a dataset can consume those API refresh requests. This limit is not increased simply by moving from Free to Pro.
Therefore, clicking the button more than 8 times is not necessarily what caused this particular error. You should check the semantic model's Refresh history to determine whether Power BI rejected the refresh because of its refresh limit, or whether Power Automate throttled the connector request before the refresh was submitted.
https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/refresh-dataset
https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-data?source=recommendations
5 Replies
- MFelix
Super User
Hi YashikaAgrawal ,
Doing the refresh call by the Power Automate counts to the number of schedule refresh só this means that sonce you are on a free license you have a limite of 8 Times per day.
So when you click more than 8 Times a day you reached the limit.
If you have a pro license you have the same limit, PPU and Higher you get to 48 Times as a limit.
Regards
Miguel Félix
- rajendraongole1
Super User
Hi YashikaAgrawal - If the semantic model is on shared capacity, Power BI documents a limit of 8 refresh requests per day for API-triggered refreshes. So a Power Automate button that calls Refresh a dataset can consume those API refresh requests. This limit is not increased simply by moving from Free to Pro.
Therefore, clicking the button more than 8 times is not necessarily what caused this particular error. You should check the semantic model's Refresh history to determine whether Power BI rejected the refresh because of its refresh limit, or whether Power Automate throttled the connector request before the refresh was submitted.
https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/refresh-dataset
https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-data?source=recommendations
- v-saisrao-msft
Community Support
HI YashikaAgrawal,
Have you had a chance to review the solution shared by MFelix rajendraongole1 ShivekMaharaj ? If the issue persists, feel free to reply so we can help further.
Thank you.
- v-saisrao-msft
Community Support
Hi YashikaAgrawal,
Checking in to see if your issue has been resolved. let us know if you still need any assistance.
Thank you.
- ShivekMaharaj
Community Champion
Hi YashikaAgrawal,
I would add one distinction here because there are two separate throttling limits that can produce similar symptoms.
The Power BI connector used by Power Automate has its own connector throttling limit of 100 API calls per connection per 60 seconds. Microsoft treats connector throttling separately from Power BI's semantic-model refresh quota.
Power BI also has a separate refresh limitation. For a semantic model on shared capacity, API-triggered refreshes are limited to eight requests per day, including scheduled refreshes. Manual Refresh now operations started directly from the Power BI service UI are not included in that eight-refresh limit.
So I would first open the failed Power Automate run, expand the "Refresh a dataset" action, and check the actual status code and response.
If you see a 429 / connector-throttling response, check whether the flow is retrying, being clicked repeatedly, or whether other flows are using the same Power BI connection.
If the response explicitly says that the Power BI refresh limit has been reached, then the shared-capacity eight-refresh quota is the relevant limitation.
One other clarification: the 48-per-day figure applies to scheduled refresh slots on PPU/Premium/Fabric capacities. API refreshes on those capacities are instead governed by available capacity resources rather than a fixed 48-request daily limit.
So I would not conclude that the Free license itself is necessarily the cause until you inspect the failed action's response.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.