Forum Discussion
Dataset refresh via Power Automate Flow - clarifications
Hi mollycat ,
Unfortunately, there’s no sneaky way around this one in Premium capacity, anything that refreshes your dataset via Power Automate (or any other API) does count toward the 48-per-day limit for that dataset, even if you trigger it manually with a button inside the report. The only refreshes that don’t count are when you (or someone with permission) click REFRESH NOW in the Power BI Service. The good news is you can add a Power Automate button in the report so end users can kick off a refresh themselves it just means each click will still eat into that 48-refresh daily quota. If you really need more than 48 automated/API refreshes a day, the only real workaround today is to go through the XMLA endpoint, which doesn’t have the same cap.
More details here in Microsoft’s official documentation: Data refresh in Power BI - Power BI | Microsoft Learn
Hope that clears things up. If the above solution works for you, please accept it as the solution so that other community members with similar issues can benefit.
Regards,
Akhil.
Hi mollycat ,
Unfortunately, there’s no sneaky way around this one in Premium capacity, anything that refreshes your dataset via Power Automate (or any other API) does count toward the 48-per-day limit for that dataset, even if you trigger it manually with a button inside the report. The only refreshes that don’t count are when you (or someone with permission) click REFRESH NOW in the Power BI Service. The good news is you can add a Power Automate button in the report so end users can kick off a refresh themselves it just means each click will still eat into that 48-refresh daily quota. If you really need more than 48 automated/API refreshes a day, the only real workaround today is to go through the XMLA endpoint, which doesn’t have the same cap.
More details here in Microsoft’s official documentation: Data refresh in Power BI - Power BI | Microsoft Learn
Hope that clears things up. If the above solution works for you, please accept it as the solution so that other community members with similar issues can benefit.
Regards,
Akhil.
Thank you Anonymous, this is the information I needed! A few quick follow ups:
1. For the manual refresh (that does not count towards the capacity limit), I understand from what you've explained that this is only available in the Power BI workspace, meaning there is no way for a user to trigger this from within the App, is that correct? This is assuming that they do have access to the gateway, which I believe is the requirement to be able to do a manual refresh.
2. I've found some helpful information about the XMLA endpoint and will definitely explore it as an option. If you have used this method, have you found that there are any major challenges or considerations based on your experience?
3. In the event that a user(s) trigger the flow and the 48 refresh limit is reached, what happens after that? Does Power BI just reject the refresh? Is an email triggered to the semantic model owner, or is there an error?
Again, thank you so much!
