← All guides

Power BI Scheduled Refresh Not Working: Causes and Fixes

The most common causes are a disabled schedule, expired credentials, an offline gateway, or a timeout. Check Refresh history first.

Work through the checks below in order. The first error often explains every symptom that follows.

Read the refresh history first

The report contains old numbers, but the reason is not clear from the report itself.

A scheduled refresh can fail for several reasons. Looking at settings, credentials, or the gateway without reading the error first can send you in the wrong direction.

Open the settings for the semantic model, formerly called a dataset, and select Refresh history. Check the status, start time, duration, and error message for the latest attempts. Look for a pattern, such as four failures in a row or a duration that keeps increasing. Read Refresh history first. Then check Gateway and cloud connections. Check Data source credentials after that.

The schedule shows Disabled

The schedule is set to Disabled, and you might also receive an email saying scheduled refresh has been disabled.

Power BI deactivates a schedule after four consecutive failures or after an error that needs a settings change, such as invalid or expired credentials. The four-failure threshold is fixed. Turning it on without fixing the original error will usually start the same failure cycle again. Power BI also pauses scheduled refresh after two months of inactivity, which means nobody has visited a dashboard or report built on that semantic model. A view by any user counts, including one through an app or embedded report, and resets the inactivity period. The owner receives an email, and the schedule shows Disabled.

If failures caused the problem, read the last error and fix that cause first. Then set Configure a refresh schedule to On and select Apply. If you see scheduled refresh disabled due to inactivity, open a report that uses the semantic model. Then return to the settings and enable the schedule if needed.

Refresh now works, but the schedule does not

A manual Refresh now can still run when Power BI has turned off the schedule after four failures in a row or paused it after two months with no views. A working manual refresh does not prove that the schedule is on.

The daily refresh limit counts scheduled refreshes and refreshes started through the API. It does not count a manual Refresh now started from the screen. Power BI Pro allows eight per day. Premium or Microsoft Fabric capacity allows 48 per day.

The schedule runs in the time zone selected in the semantic model settings. A scheduled refresh can start up to one hour late. On-demand refreshes and refreshes started by Power Automate do not send failure emails.

Check the schedule toggle and its time zone in the settings. Read Refresh history for the scheduled attempts only. Count the scheduled slots used that day.

Credentials are missing or expired

Refresh history reports that credentials are missing, invalid, or expired.

A changed or expired data source password must also be updated under Data source credentials. Each user has one set of credentials for each data source, and every semantic model has one owner. You need to take ownership before you can update credentials for a model you do not own. Some sources, including SharePoint Online and Dynamics, use a Microsoft Entra ID OAuth token that expires in about one hour. A load that runs longer can therefore end with a credentials error even when the sign-in worked at the start.

Update Data source credentials in the semantic model settings. If another account owns the model, select Take over first. Cached credentials can also cause repeated sign-in problems. Clear the browser cache, sign in again, and open https://app.powerbi.com?alwaysPromptForContentProviderCreds=true to force a new credentials prompt.

The gateway is offline

Gateway connection shows as disabled, a personal gateway shows offline, or you receive GatewayNotReachable while setting credentials.

Gateway connection is disabled if no gateway is available. A personal gateway shows offline when it is unavailable. GatewayNotReachable can also mean that the on-premises data gateway is outdated. Microsoft supports only the latest six gateway versions. A semantic model can use only one gateway connection. If one query combines an on-premises source with a cloud source, the cloud source must go through that gateway too.

Open Gateway and cloud connections and check the gateway status. Make the gateway available, or update it if its version is too old. If the query mixes cloud and on-premises data, confirm that both are assigned through the same gateway connection. With an on-premises data gateway, the gateway administrator manages the credentials. Data source credentials can therefore appear greyed out to the semantic model owner. That is expected. Ask the gateway administrator to check or update them.

The Power BI refresh times out

Refresh history shows a long duration followed by a failure, or a Power BI refresh timeout appears to be a credentials problem when a token expires during the load.

On shared capacity, a refresh must finish before the two-hour limit. On Premium capacity, the maximum is five hours. Shared capacity also limits the uncompressed data processed during refresh to 10 GB. The maximum imported model size there is 1 GB. Refreshes started through the XMLA endpoint are not bound by the five-hour limit, as Chris Webb explains in his write-up on the two-hour and five-hour import refresh limits.

Compare the failed duration with the limit for your capacity. If the refresh is close to that limit, reduce the data processed or shorten the load before testing again. If a SharePoint Online or Dynamics refresh fails near one hour with a credentials message, check the OAuth token issue as well.

The refresh runs out of memory

On Premium or Microsoft Fabric capacity, a refresh can be canceled with Query memory limit exceeded or This operation was canceled because there wasn't enough memory to finish running it. The error code is 0xC13E0003.

A refresh must hold the model, the new copy being processed, and temporary structures in memory at the same time. Moving a workspace to a different capacity can lower the per-model memory limit.

For these refresh memory errors, refresh only the tables or partitions that changed by using incremental refresh. Remove unused columns and rows. Reduce high-cardinality columns. Move calculated columns and tables back to the source.

The refresh succeeded but the report is old

Refresh history says Completed, but the report or dashboard still shows yesterday’s numbers.

First check the scheduled time and its time zone. Power BI aims to start within 15 minutes of the scheduled slot, but a refresh can begin up to five minutes early or as much as one hour late. Dashboard tiles can take another 10 to 15 minutes to show refreshed data. Power BI Pro allows up to eight scheduled refreshes per day. Premium Per User and Premium or Microsoft Fabric capacity allow up to 48. A report published from Power BI Desktop refreshes in the Power BI service only on its schedule and within these limits.

Use Refresh history to find the actual start and completion time. Confirm that the report uses the same semantic model whose history you checked. Allow for a late start and the dashboard tile delay. If you expected more than eight daily refreshes on Power BI Pro, review the schedule against that limit.

Keep the refresh running

Use this checklist once the refresh works again.

  • Send failure emails to a shared address with an account in the same Microsoft Entra tenant. External addresses are not supported.

  • Keep the on-premises data gateway on a machine that stays on, not a laptop that travels or sleeps.

  • Make an account that will not leave the company the semantic model owner.

  • Review Refresh history once a week. Check failures, durations, and repeated warnings.

Power BI emails the owner after scheduled refresh failures and when it disables a schedule after consecutive failures. Added contacts receive those alerts too. Check spam filters if the messages do not arrive. On-demand refreshes and refreshes started by Power Automate do not send failure emails.

When to hand it over

Hand the problem over if Refresh history shows an error you cannot read, or if the refresh breaks again after a fix.

We fix a broken refresh inside 48 hours for a fixed price agreed first. You receive a plain note explaining what broke, what we changed, and how to stop it from recurring.

Frequently asked questions

What does “scheduled refresh greyed out” mean?

Check which setting is greyed out. If Gateway connection shows as disabled, no available gateway was found. If Data source credentials is greyed out while the model uses an on-premises data gateway, the gateway administrator manages those credentials. If you need to update credentials on a model you do not own, select Take over first.

What does “at least one data source is missing credentials” mean?

One of the sources used by the semantic model does not have usable credentials for your account. Open Data source credentials and sign in again. If the model uses an on-premises data gateway, ask the gateway administrator to update the credentials there.

Why was scheduled refresh disabled after nobody used the report?

Power BI pauses the schedule after two months without a view of any report or dashboard built on the semantic model. Open a report that uses the model, then enable the schedule again if it remains Disabled.

How we checked this: every rule on this page was checked against Microsoft Learn on 10 November 2026.

For a free first read, send the Refresh history error or the report name. We send one page back within five business days. It is free, and we change nothing in your systems.

Inside 48 hoursFix itThe fault is found, fixed and tested on a live run. You get a plain note on what broke and how to stop it recurring.See the offer