Scheduled refresh also causing api call

[lzdkng]

Good morning,

I have a simple Power BI dashboard that gets it's data from an excel spreadsheet in a Sharepoint library. The spreadsheet gets updated 5 times/day so I set up a scheduled refresh on the Power BI dashboard that refreshes right after that. It has been working fine for several weeks, but last week I started getting error of too many refreshes in 24 hour period (Limit is 8). When I looked at refresh history it showed this

For every scheduled refresh there is now a "Via API" that goes with it. When I turned off the scheduled refresh all of the "Via API" stopped too. No one is doing any API calls or pushes to the dashboard. Nothing has been updated or changed recently. Any ideas on what the cause is and how to fix?

Thanks!

[Anonymous]

Hi @lzdkng ,

This is amazing! If you have not configured API refresh, API refresh will not occur when you schedule a refresh, and you can try the following methods:

1. Try disabling and re-enabling the scheduled refresh to see if that resolves the issue.
2. Try extending the refresh interval to avoid too many refreshes.

Below is the Microsoft’s official link:

Enhanced refresh with the Power BI REST API - Power BI | Microsoft Learn

Best Regards,

Xianda Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[lzdkng]

Good morning. Thanks for the reply.

Disabling and re-enabling the scheduled refresh did not resolve the issue. When I disabled the scheduled refresh, the api refresh stopped too.

Yes I can change the number of refreshes but this means that I only have 4 refreshes a day instead of 8. That is not really a fix.

I found a way to fix it, but I wouldn't call it a solution. I deleted the published report, re-published the exact same pbix file to the same workspace, set up the same scheduled refresh, and it magically started working. While this fixed the problem it is not an optimal solution as I still have to go back and set up all of the permissions. I suspect that Microsoft pushed some update and that caused the issue to occur.