When a Power BI scheduled refresh fails, start with the refresh history: in the Power BI service, open the workspace, select the semantic model, then Refresh and Refresh history. The error message there almost always points to one of seven causes: expired or missing credentials, a gateway problem, a refresh that ran past the time limit, a model that ran out of memory, a data source Power BI can't refresh on its own, a file that moved, or a schedule that Power BI switched off after repeated failures. Fix the cause, run Refresh now to confirm it works, then turn the schedule back on.
First, read the error
Don't guess. In the Power BI service:
- Open the workspace and select the semantic model (what Power BI used to call a dataset).
- Select Refresh, then Refresh history.
- Open the failed attempt and read the full error. Copy the details if you need to search or send them to someone.
If you'd like to hear about the next failure sooner, open the semantic model's settings and check the refresh failure notification options. By default the model's owner gets an email. You can add other people under "Email these contacts when the refresh fails." Note that failures on manual refreshes don't send those emails.
Cause 1: credentials expired or are missing
This is the most common one. Someone changed a password, a sign-in token expired, or the model was published by a person who has since left and their credentials went with them.
Open the semantic model's settings and expand Data source credentials. Any source with a problem shows a warning. Select Edit credentials, sign in again, and save. If the error says a source is missing credentials, scheduled refresh stays disabled until you fill them in.
If the model's owner has left the company, another workspace member can take over the model in its settings, then enter their own credentials. Our post on credentials and data source errors goes into more detail.
Cause 2: the gateway is offline or out of date
If your data lives on a server in your office (SQL Server, files on a shared drive, an on-premises ERP), the refresh runs through an on-premises data gateway. If that gateway is offline, every refresh that depends on it fails. Cloud sources such as Azure SQL Database or SharePoint Online usually don't need a gateway.
Check the gateway status under Settings, then Manage connections and gateways. The usual causes are a gateway machine that sleeps or restarts overnight, a gateway version more than six months old, or blocked network ports. Our guide to why your gateway keeps disconnecting walks through each one.
Cause 3: the refresh took too long
Microsoft stops a scheduled refresh that runs past a time limit: 2 hours for a model on shared capacity (a normal Pro workspace) and 5 hours on Premium or Fabric capacity. A refresh that used to take 40 minutes can creep past the limit as your data grows.
Look at the duration of recent successful refreshes in the refresh history. If they're getting longer, shrink what the refresh has to do: remove columns and rows you don't use, and set up incremental refresh so Power BI only reloads recent data. A slow source query (often a SQL view doing too much work) is the other usual suspect.
Cause 4: the model ran out of memory
Errors that mention memory, such as "memory limit exceeded" or "there wasn't enough memory to finish running it," mean the model is too big for the capacity it's on. A Pro workspace caps a model at 1 GB. The fix is almost always to make the model smaller before paying for more capacity. We cover how in fixing memory limit exceeded errors.
Cause 5: a data source the service can't refresh
Some queries work fine in Power BI Desktop but can't be refreshed in the service. Microsoft calls the most common case a dynamic data source: a query that builds its connection address on the fly, for example by looping through a list of web addresses or file paths. In most cases the service can't refresh those.
In Power BI Desktop, open Power Query, then Data source settings. If a source can't be refreshed in the service, you'll see a warning there. The fix is usually to rewrite the query so the base address is fixed and only the parameters change. That's a small rewrite, but it helps to know Power Query well.
Also check privacy levels. Power BI Desktop doesn't publish your privacy settings, so after publishing you have to set them again on the data source in the service. Mismatched settings can make a refresh fail or run very slowly.
Cause 6: a file moved or was renamed
If the model reads an Excel or CSV file, moving it, renaming it or changing a sheet name breaks the refresh. The error usually names the file or says a column or table can't be found. Put the file back, or open the report in Power BI Desktop, point the query at the new location, and publish again.
Files on a personal OneDrive are a common trap: if the person who owns the file leaves, the file goes with them. Keep source files in a shared SharePoint library instead.
Cause 7: Power BI switched the schedule off
Power BI turns off a scheduled refresh after four failures in a row, and it pauses the schedule if nobody has opened a report or dashboard built on the model for two months. In both cases the schedule shows as disabled and the owner gets an email.
Fix whichever cause above made it fail, run Refresh now to make sure it works, then turn the schedule back on under Refresh, then Schedule refresh. For the inactivity pause, opening a report built on the model or running a manual refresh resumes it.
One more thing to check: the schedule itself
A Pro workspace allows up to 8 scheduled refreshes per day. Premium Per User and Premium or Fabric capacity allow up to 48. If you set more times than your license allows, some won't run. Refreshes you start by hand with Refresh now don't count toward the 8.
When to call someone
Most failed refreshes are credentials or a gateway, and you can fix those yourself in a few minutes with the steps above. It's worth getting help when the error message doesn't make sense, when refresh fails only some of the time, when the model is close to its time or memory limits, or when a report your team needs this morning is showing yesterday's numbers.
That's what our $299 Power BI fix is for: a senior consultant finds and fixes one problem, and if we can't fix it, you don't pay. If refreshes keep failing because the setup underneath needs rework, see Power BI advisory.
Sources: Microsoft Learn, Configure scheduled refresh, Data refresh in Power BI, Troubleshoot refresh scenarios.