Help for owners
My Power BI report stopped refreshing
Short answer
If a Power BI scheduled refresh fails four times in a row, Power BI disables it, so reports can go stale silently. Common causes are expired credentials, an offline or outdated gateway, a refresh that runs past the time-out, or a data set that exceeds size limits. Read the refresh history, fix the cause, then re-enable the schedule.
Does this sound like your situation?
- The report shows old numbers and the last refresh date is days ago.
- I got an email saying the refresh failed.
- The refresh history shows a credentials or gateway error.
- The refresh used to take minutes and now fails after hours.
- It stopped after a password change or after someone left.
Why does this happen?
Power BI disables the schedule after repeated failures
If a scheduled refresh fails four times in a row, Power BI disables it. You need to address the underlying problem and re-enable the schedule.
Confirmed by learn.microsoft.com
Credentials expired or a password changed
Microsoft lists expired cached credentials and password changes as a cause, with a documented way to force the credentials to be requested again.
Confirmed by learn.microsoft.com
The gateway is out of date or unreachable
Microsoft says to verify that the gateway version is up to date and that the report has a gateway selected. It supports only the last six versions of the on-premises data gateway, so an old one causes failures.
Confirmed by learn.microsoft.com
A refresh runs past the time-out
Scheduled refreshes for imported semantic models time out after two hours, or five hours in Premium and Fabric workspaces. The time-out applies to each attempt.
Confirmed by learn.microsoft.com
Size and token limits
Imported semantic models are limited to 1 GB, and in shared capacity 10 GB of uncompressed data is processed during refresh. Sources that use Microsoft Entra ID OAuth can fail with a credentials error if loading takes over an hour, since that token expires in about an hour.
Confirmed by learn.microsoft.com
What can I do about it today?
- Open the refresh historyLook at the failure message and the time of the first failure. Copy it exactly.
- Check the schedule is still onA disabled schedule shows as off. Do not re-enable it before you know why it failed, or it will fail again.
- Find out who set up the credentialsAsk whether that person changed a password or left.
- Check the gateway computerIf the report reads from an office server, ask whether the gateway machine is on and updated.
- Tell people the report is staleA note on the report prevents decisions on old numbers.
When should I bring someone in?
- The refresh fails every time and the cause is not clear.
- The report feeds finance or client reporting.
- The data set is very large and refreshes take hours.
How do I handle it?
- Read the refresh historyI look for the first failure and what changed just before it.
- Fix the cause, not the scheduleCredentials, gateway, queries or model size are corrected before the schedule is turned on.
- Shrink what is refreshedUnneeded columns and rows are removed and large tables refreshed in parts.
- Set up an alertFailed refreshes notify a shared address rather than one person.
- Write down the setupWho owns the credentials, which gateway is used and when it runs.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Why did my schedule turn itself off?
Microsoft states that four failures in a row disable a scheduled refresh.
How long can a refresh run?
Two hours for imported semantic models, five hours in Premium and Fabric workspaces, per attempt.
Do I need a gateway?
If the data sits on a private network or on-premises, usually yes. Microsoft's guidance is to check the report has a gateway selected.
Can the data be refreshed in parts?
Microsoft suggests incremental refresh for large semantic models, which reduces the amount refreshed.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.