Why is My Power BI Data Not Refreshing?

Nothing brings a data-driven meeting to a grinding halt faster than a Power BI dashboard showing last week's numbers. You've built the report, hit publish, and scheduled it to refresh, but the data is clearly stale. This article cuts through the confusion and walks you through the most common culprits behind Power BI refresh failures, providing clear, step-by-step solutions to get your data flowing again.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

First, Understand the Two Types of Refresh

Before diving into troubleshooting, it's essential to know which type of "refresh" you're dealing with. Power BI has two distinct contexts for refreshing data, and knowing the difference will help you pinpoint the problem faster.

1. Manual Refresh in Power BI Desktop

This is the refresh you perform while building or editing your report on your local computer. You click the "Refresh" button in the Home ribbon, and Power BI Desktop contacts the data sources directly from your machine to pull in the latest information.

Failures here are usually straightforward. Because you're initiating the refresh yourself, any errors (like a bad file path or an incorrect server name) pop up immediately. These problems are typically related to your direct connection to the source.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

2. Scheduled Refresh in Power BI Service

This is the automated refresh that happens in the cloud after you've published your report. You configure it in the Power BI Service (the web version) to run at specific times, like every morning at 8 a.m. This is where most refresh problems occur, as the process runs in the background on Microsoft's servers, which don't have direct access to your local computer or private network.

Scheduled refresh failures are thornier because they involve more moving parts, such as gateways, cloud authentication, and different service permissions. The rest of this guide will focus on troubleshooting these common scheduled refresh issues.

Common Causes for Refresh Failures and How to Fix Them

Here are the primary reasons your data isn't refreshing in Power BI Service, starting with the most frequent offenders.

Problem 1: Expired or Incorrect Data Source Credentials

This is arguably the most common issue. Your data source password - whether it's for a database, a SharePoint site, or a SaaS application - has changed, but Power BI Service is still trying to use the old one. The refresh attempt fails because it can't log in to get the data.

• How to Spot It: The refresh failure email or the refresh history will often mention "invalid credentials" or "login failed."
• The Fix: Update your credentials in the Power BI Service.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Problem 2: Data Gateway Issues

If your data source is "on-premises" (meaning it's not in the cloud, like an SQL Server in your office data center or an Excel file on your shared network drive), Power BI Service needs a bridge to reach it securely. This bridge is the Power BI Data Gateway.

Problems with the gateway are the second major cause of refresh failures. The gateway is a piece of software installed on a server or computer within your network that must be on and connected to the internet for the refresh to work.

Common Gateway Problems:

• Gateway is Offline: The computer hosting the gateway is turned off, asleep, or disconnected from the internet. Remember, the gateway is an active bridge, and if it's down, traffic can't pass through.
• Outdated Gateway Software: Microsoft releases monthly updates for the gateway. An outdated version can lose compatibility with the Power BI Service.
• Network or Firewall Issues: Your company firewall might be blocking the necessary outbound TCP ports that the gateway uses to communicate with Power BI.

The Fix:

1. Confirm the Gateway is Online: First, ensure the machine running the gateway software is powered on and connected to the internet. Second, check that the "On-premises data gateway service" is running in Windows Services (you can search for "Services" in the start menu).
2. Update the Gateway: Remote into the gateway machine and update the Power BI Gateway software to the latest version.
3. Check Network Connectivity: In the Power BI Gateway software, there is a “Diagnostics” tab with a network port test. Run this test to ensure it can connect to the necessary Azure Service Bus endpoints. If it fails, you may need to speak with your IT team about firewall rules.

Problem 3: Changes to the Data Source Structure

This happens all the time. Your Power Query steps are a specific set of instructions, and if the data source changes unexpectedly, those instructions break.

Imagine your query expects a column named "SalesAmount," but someone in the source database renames it to "Revenue." The next time Power BI tries to refresh, it will look for "SalesAmount," fail to find it, and the refresh will error out.

Common Source Change Problems:

• A column was renamed or deleted.
• A table/sheet name was changed.
• For file-based sources (like CSV or Excel), the file was moved, renamed, or deleted.
• Data types have changed (e.g., a column that was numeric is now text).

The Fix:

1. Identify the Error: Power BI's refresh history usually provides a detailed error message, like "The column '[ColumnName]' of the table was not found."
2. Fix it in Desktop: Download the .PBIX file from the service. Open it in Power BI Desktop and go to "Transform data" to open the Power Query Editor.
3. Find the Broken Step: In the "APPLIED STEPS" pane on the right, you'll see a step with a red or yellow warning icon. This is where the process failed.
4. Correct the Step: Click on the broken step and fix the underlying issue. This might involve renaming the column back in your query, changing the data type, or changing the source to point to the new filename or location.
5. Republish Your Report: Once the refresh works correctly in Desktop, save and republish the report to Power BI Service.

Problem 4: Refresh Timeouts

A standard Power BI refresh is limited by time. For datasets in a Shared capacity (with a Pro license), the limit is 2 hours. For datasets in Premium capacity, it's 5 hours. If your data import and transformation takes longer than that, the refresh will be automatically canceled.

This often happens as your data grows. A report that once refreshed in 30 minutes may now take over 2 hours as your transactional database expands.

The Fix:

• Optimize Your Power Query Transformations: The most effective solution is to make your queries more efficient. Filter out unnecessary rows and unneeded columns as early as possible in your Power Query steps. This reduces the amount of data Power BI has to process.
• Enable Incremental Refresh: If you're working with very large fact tables, set up incremental refresh. This allows Power BI to only refresh new or changed data instead of refreshing your entire 50-million-row history table every time.
• Upgrade to Premium: If optimization isn’t enough, moving to a Premium capacity gives you a longer 5-hour timeout and more flexible refresh options.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Problem 5: Data Privacy Level Mismatches

Power BI has a feature called the "Data Privacy Firewall" that isolates data sources to prevent data from being unintentionally sent from one source to another. If Power BI Service can't determine how to safely combine data from different sources (e.g., a public web API and an internal SQL server), it will stop the refresh.

• How to Spot It: You'll get an error message like "Formula.Firewall: Query references other queries or steps, so it may not directly access a data source."
• The Fix: Make sure you have set the privacy levels correctly in both Power BI Desktop and Service. Before publishing, go to File > Options and settings > Data source settings. For each source in the list, set a privacy level (e.g., Organizational, Private, Public). Then, when you publish, ensure these match the settings in the Power BI Service's Data source credentials area. For sources within your company, setting them all to "Organizational" often solves the problem.

Proactive Tips to Prevent Refresh Failures

Fixing problems is good, but preventing them is better. Here are a few best practices.

• Subscribe to Failure Notices: In the dataset settings, you can check a box to receive an email notification when a refresh fails. This is much better than discovering the stale data yourself.
• Regularly Check Refresh Status: Make a habit of checking your Refresh History in the Power BI Service to see if everything's running smoothly and how long refreshes are taking.
• Communicate with Data Owners: If a team makes changes to a database schema or file structure, make sure they know your report depends on them.
• Test Changes Before Publishing: Before you publish a change that adds a new source or modifies complex queries, always test a full refresh in Power BI Desktop before pushing it into the service.

Final Thoughts

Troubleshooting Power BI refresh failures is a process of elimination that usually leads to a few common areas: data credentials, gateway connectivity, or unexpected changes in the source data itself. By patiently working through these potential issues, you can identify the root cause and ensure your reports stay current and reliable.

With Power BI's powerful capabilities, there are times when you're simply trying to do analysis, but end up debugging gateways and credentials to get back to it. We created Graphed to streamline the process by connecting sources like Shopify and Salesforce, helping you build live dashboards with ease, so you'll never have to worry about stale data again.