Power BI refresh errors: common causes and how to fix them
Power BI refresh errors are failures that stop a semantic model from loading new data, so reports keep showing old numbers. Most come from a short list of causes: credentials, gateways, time-outs, memory and capacity limits. Therefore a fixed order of checks finds the cause faster than guessing. This guide follows Microsoft's troubleshooting advice in plain language.
- Check the gateway first
- Credentials expire
- Schedules can switch off
Last updated
Why do Power BI refresh errors happen?
A refresh is a chain. The service connects to a source, often through a gateway, runs the queries and loads the result into the model. Any link can break, so the message you see depends on where the chain failed.
Microsoft's guidance starts with the basics. First, confirm that the gateway runs a current version. Then confirm that the model has a gateway selected in its settings. Many failures end right there.
Change is the usual trigger. For example, someone changes a password, renames a column or moves a file. The report worked yesterday because nothing had changed yet.
Common failure messages and their likely causes
Microsoft documents these scenarios. Match the message first, then try the simplest fix.
| What you see | Likely cause | First thing to try |
|---|---|---|
| GatewayNotReachable when you set credentials | An outdated gateway | Install the latest gateway version |
| Access to the resource is forbidden | Expired or changed credentials | Sign in again and re-enter the credentials |
| Processing error with a type mismatch | A problem in the query script or an old Desktop version | Update Desktop and publish the file again |
| Scheduled refresh has stopped running | Several failures in a row | Fix the cause, then switch the schedule back on |
| Query memory limit exceeded | The refresh needs more memory than the capacity allows | Reduce the model or use incremental refresh |
| Capacity limit for refreshes exceeded | Too many refreshes at once on a capacity | Move the schedule away from peak times |
| The connection timed out or was lost | A passing network or source problem | Run the refresh again |
How to work through Power BI refresh errors in order
Work from the outside in, because the simple causes are also the most common.
Read the refresh history
First, open the refresh history of the semantic model and read the failure message. It usually names the source or the stage that failed.
Check gateway and credentials
Then confirm the gateway is online and current. After that, re-enter the data source credentials.
Test in Power BI Desktop
Next, refresh the same file in Desktop. If it fails there too, the cause lies in the query or the source.
Reduce the load
Finally, look at size and timing. A large model may need incremental refresh or a quieter time slot.
Why did scheduled refresh switch itself off?
Power BI turns a schedule off after several consecutive failures. Microsoft documents this behavior. So a model can sit stale for days when nobody watches for the notice.
The fix has two parts. First, repair the cause, because re-enabling a broken schedule only repeats the failures. Then open the settings of the model and switch scheduled refresh back on.
Notifications prevent a repeat. The same settings page lets you send failure emails to the owner and to other contacts. Therefore add a shared mailbox or a second person, not one individual alone.
What causes Power BI refresh errors on large models?
Size brings its own failures. Shared capacity limits the size of an imported model, and a scheduled refresh there has a time limit. Premium capacities allow longer runs, but they also have limits.
Memory is the next wall. When the capacity runs short, the refresh stops with a memory message. Incremental refresh helps, since it reloads only recent periods instead of the full history.
Long loads can also outlive their sign-in. With Microsoft Entra ID OAuth, a token can expire during a very long load, and the refresh then fails on credentials. So shorten the load, or split the work into smaller pieces.
Failed refresh questions from report owners
Who gets told about Power BI refresh errors?
By default, the semantic model owner receives an email when a refresh fails. The settings of the model also let you add other contacts. We recommend adding a shared mailbox, because owners go on leave and change jobs. Without a second recipient, a failed refresh can go unnoticed until a reader spots old numbers in a meeting.
Do Power BI refresh errors mean the data is lost?
No. When a refresh fails, the model keeps the data from the last successful run. Reports therefore still open, but they show older figures. The risk is that readers do not notice. So show the last refresh time on the report page, and readers can judge for themselves how current the numbers are.
Why does refresh work in Desktop but fail in the service?
The two run in different places. Desktop uses your machine, your network and your sign-in, while the service uses a gateway and stored credentials. So a source that your laptop can reach may be invisible to the service. Microsoft also notes a data type difference for columns of type Any. Check the gateway, the stored credentials and the data types first.
What does a capacity limit message mean?
It means the capacity was too busy to run more refreshes at that moment. Microsoft suggests several answers: refresh outside peak hours, space the schedules apart, use incremental refresh and simplify the model. If the message returns often, the capacity may be too small for the workload. That is a sizing decision for your administrator.
Can you fix a refresh that keeps failing?
Yes. Power BI Agency traces failing refreshes to their cause and repairs the query, the gateway setup or the model. One of our consultants works online inside your tenant, alongside your IT team. We are a division of Sataware Technologies, independent of Microsoft. Request a free 30-minute assessment. You get a reply within 2 hours.
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.