// troubleshooting guide · microsoft power bi
Power BI Scheduled Refresh Failed
- Status
- Workaround available
- platforms:
- Power BI service (web)
- updated:
- November 16, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · power-bi/scheduled-refresh-failed6 FIXES
// quick answer
Scheduled refresh usually fails because of expired data source credentials, a gateway problem or a timeout. Update the credentials in the semantic model settings, check the gateway, then turn the schedule back on (Power BI disables it after four failures in a row).
Most likely fix: Read the error in refresh history
How to fix it
// try these in order, the most common fix is first
FIX 1Read the error in refresh history
- 01In the Power BI service open the workspace
- 02Hover the semantic model, select More options (...) > Refresh history
- 03Open the failed entry and note the error text and data source named
Did this fix it?FIX 2Update data source credentials
- 01Open the semantic model Settings
- 02Expand Data source credentials and select Edit credentials for each source
- 03Sign in again and save
- 04If it still says access forbidden, clear the browser cache and open https://app.powerbi.com?alwaysPromptForContentProviderCreds=true to force a fresh credential prompt
Did this fix it?FIX 3Check the gateway connection
- 01In semantic model Settings expand Gateway and cloud connections
- 02Make sure a gateway is selected and shows as running
- 03Update the on-premises data gateway to the latest version
Did this fix it?FIX 4Re-enable the schedule
- 01After fixing the cause, expand Refresh in the semantic model settings
- 02Turn Configure a refresh schedule back On and save
- 03Trigger Refresh now once to confirm it succeeds
Did this fix it?FIX 5Shrink long or large refreshes
- 01Remove unused columns and rows in Power Query
- 02Use incremental refresh for big fact tables
- 03Split a very large model into smaller ones or move it to Premium/Fabric capacity for the 5-hour timeout
Did this fix it?FIX 6Republish from Desktop if it still fails
- 01Open the .pbix in an up-to-date Power BI Desktop
- 02Refresh locally to confirm the queries work
- 03Publish again, then set credentials and schedule
Did this fix it?
SANDBOX · power-bi RUNS IN YOUR BROWSER
Try it: browse a sample shop and watch visitors, funnels and live data arrive
A hands-on Microsoft Power BI-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
You get a 'refresh failed' email, the refresh history shows Failed, dashboards show old data, or the schedule toggle is turned off by itself.
Why it happens
- C-01Expired or changed data source credentials (password change)
- C-02On-premises gateway offline, outdated or not selected
- C-03Refresh exceeded the 2-hour timeout (5 hours on Premium/Fabric)
- C-04Microsoft Entra ID OAuth token expired during a load longer than about an hour
- C-05Model exceeds 1 GB or 10 GB uncompressed refresh limit on shared capacity
- C-06Four consecutive failures auto-disabled the schedule
// this guide also covers
- power bi scheduled refresh failed
- power bi refresh not working
- power bi scheduled refresh disabled
- power bi refresh failed credentials
- power bi refresh timeout
Still not working?
If Microsoft Power BI keeps failing, you're not alone. See every Microsoft Power BI problem users report or the alternatives people switch to.
Done fighting Microsoft Power BI? Our small team builds your own Microsoft Power BI alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to usOther Microsoft Power BI errors
- Power BI Gateway Offline or Could Not Be Reached
- Why Is My Power BI Report So Slow?
- Power BI Desktop Refresh and Power Query So Slow
- Power BI Desktop Not Opening or Stuck on Splash Screen
- Can't Sign In to Power BI Desktop
- Power BI Visual Has Exceeded the Available Resources
- Power BI Error: The Key Didn't Match Any Rows in the Table
- Power BI DataFormat.Error: We Couldn't Convert to Number