← Back to Error Directory

"We Couldn't Refresh" Power Query Error — Complete Fix

A refresh failure can mean four completely different things — here's how to tell which one you're dealing with.

Table of Contents

1. Why This Message Is So Generic

Power Query's refresh mechanism touches several independent systems — file paths, network connections, authentication tokens, and privacy classifications — and a failure in any one of them produces a broadly similar "we couldn't refresh" message. Clicking "Details" or "Show details" in the error dialog is essential, since the underlying specific cause is buried there rather than in the headline message.

2. Interactive Demo: Refresh Failure Diagnostic

Walk through the same diagnostic logic Power Query effectively performs during a refresh attempt.

3. Cause 1: Expired or Missing Credentials

Data sources requiring authentication (databases, web APIs, cloud services like SharePoint) store credentials that can expire, particularly OAuth-based tokens that have a defined validity period. When the stored credential is no longer valid, the refresh fails at the authentication stage before any data can even be retrieved.

4. Cause 2: Source File Moved, Renamed, or Deleted

If the query's source is a file path (like a CSV, Excel file, or folder), and that file or folder has since been moved, renamed, or deleted, Power Query cannot locate it during refresh. Unlike a simple worksheet formula's #REF!, this shows up specifically as a refresh failure rather than an immediate cell-level error, since the connection itself fails before any data reaches the worksheet.

5. Cause 3: Privacy Level Conflicts

This is a Power Query-specific concept with no equivalent elsewhere in Excel. Every data source is classified with a privacy level — Public, Organizational, or Private — and Power Query restricts certain combinations of privacy levels from being combined (merged or appended) together during the same refresh operation, specifically to prevent private data from one source being inadvertently sent to or combined with a more public source in ways the user didn't explicitly intend.

6. Cause 4: Source Temporarily Unreachable

Network-dependent sources (databases, web-based data, cloud files) can simply be temporarily unavailable due to server maintenance, network outages, or connectivity issues on either end — this is the most transient of the four causes and often resolves itself without any local configuration changes.

7. Fixing Credential Issues Step by Step

  1. Go to Data tab → Queries & Connections.
  2. Right-click the affected query and select Data Source Settings.
  3. Select the specific source showing an issue, then click Edit Permissions.
  4. Clear the existing (likely expired) credentials, then re-enter or re-authenticate using the appropriate method for that source type (Windows credentials, database login, or OAuth sign-in).

8. Fixing Privacy Level Conflicts

  1. Go to Data tab → Queries & Connections → right-click the query → Data Source Settings.
  2. Select each relevant source and click Edit Permissions to view or change its assigned privacy level.
  3. Alternatively, under File → Options and Settings → Query Options → Privacy, you can (with appropriate caution) select "Ignore the Privacy Levels and potentially improve performance" — this bypasses the privacy check entirely and should only be used when you're certain the data combination poses no actual sensitivity concern.

9. Frequently Asked Questions

Why does Power Query say it couldn't refresh?

This generic message covers several possible causes: expired or missing credentials for the data source, the source file or database being moved or renamed, a privacy level conflict between combined data sources, or the underlying source being temporarily unreachable.

What is a privacy level conflict in Power Query?

Power Query classifies each data source as Public, Organizational, or Private, and blocks certain combinations of sources with different privacy levels from being merged together during refresh unless the privacy levels explicitly allow it, to prevent unintended data leakage between sources.

How do I fix a Power Query refresh error caused by expired credentials?

Go to Data tab, click Queries & Connections, right-click the affected query, select Data Source Settings, then Edit Permissions to re-enter or refresh your credentials for that specific source.

Related Guides

Editorial Disclaimer: This guide is developed to the best of our domain knowledge and tested against Excel 2019+, Microsoft 365, and Google Sheets. Content is updated continuously as spreadsheet calculation engines evolve.