What is the Pending Icon in Power BI?

If you've spent any time at all in Power BI's Power Query Editor, you've probably seen it: a small, unassuming icon next to your query that says "Pending outgoing request to a source." While your other queries have finished loading, this one just sits there, an icon of inactivity while you just want to get your report built. This article will break down exactly what that pending icon means, the common reasons it appears, and how you can troubleshoot the underlying issues to get your data flowing smoothly again.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

What is an Outgoing Source Query Anyway?

Before we dive into the problems, let's quickly define what Power BI is actually doing behind the scenes. When you connect to a data source (like a SQL database, a Salesforce account, or even an Excel file) and start applying transformation steps in the Power Query Editor, Power BI isn't immediately pulling all the data into your computer. Instead, it's building a list of instructions - a "query."

Think of it like giving a research assistant a to-do list for the library:

• The Data Source: This is the library. It contains all the books (data).
• The Query: This is your set of instructions. "Go to the Business section, find all the books on Q4 sales, ignore any published before 2020, and only bring back the title and chapter one."
• Power Query: This is your research assistant, who takes the instructions and goes to the library to fulfill the request.

The "Pending outgoing request to a source" icon simply means your research assistant has the list of instructions and is standing at the library counter, waiting for the librarian to retrieve the books. The work is waiting on the source to respond. The delay isn't happening inside Power BI, it's happening in the communication between Power BI and your data source.

Why You're Seeing the "Pending Outgoing Request" Icon

While the icon itself is simple, the reasons behind the delay can range from simple to complex. Here are the most common culprits that cause Power BI to wait on a data source.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

1. Your Query Folding is Broken

This is, by far, the most common reason for that dreaded pending icon, especially with database sources like SQL, PostgreSQL, or Snowflake. To understand this, you need to understand the concept of query folding.

What is Query Folding?

Query Folding is a Power Query feature where the transformation steps you apply (like filtering rows, removing columns, or grouping data) are translated into a single, efficient query in the native language of the source system (e.g., SQL). In our library analogy, instead of your assistant bringing back every single book from the Business section for you to sort through at your desk, they give the librarian one highly specific request. The librarian does all the filtering and sorting in the library and returns only the exact information you wanted.

When query folding is working, it's incredibly efficient because the source system - which is designed for heavy data processing - does all the work.

When query folding "breaks," it means you applied a transformation step that Power Query can't translate into the source's native language. When this happens, Power BI has no choice but to stop folding. It executes the folded part of the query, pulls the entire, unfiltered result set into your computer's memory, and then performs the rest of the transformations locally. This is slow, resource-intensive, and a primary cause of the "pending" icon as it waits for that massive, unrefined dataset to be transferred.

Common reasons query folding breaks include:

• Unsupported Transformations: Using steps that don't have a direct equivalent in the source language. For example, adding an 'Index Column' has no SQL equivalent, so it almost always breaks folding.
• Complex Custom M Code: Writing custom functions or intricate logic in the M language that the source database cannot interpret.
• Mixing Data Sources: If you merge a SQL query with data from an Excel file, folding breaks at the point of the merge. The SQL server has no way of accessing an Excel file on your machine, so all the data must be brought into Power BI to be combined.

2. The Data Source is Slow or Overloaded

Sometimes, Power BI isn't the problem at all. Your data source itself might be the bottleneck. Power BI has sent the query, but the source server is taking a long time to process the request and send the data back.

• Overloaded Database: The company's SQL server might be busy running other critical operations, and your analytics query is low on its priority list.
• API Rate Limits: When connecting to SaaS platforms via an API, you're often subject to rate limits. If your query asks for too much data too quickly, the API might throttle your request, forcing Power BI to wait.
• Network Latency: If you're pulling a large dataset from an on-premise server over a slow network connection or VPN, the physical transfer of data can be the main cause of the delay.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

3. Data Source Privacy Level Mismatches

This is a subtle but surprisingly common issue. To prevent sensitive data from one source from being accidentally leaked to another, Power BI has data privacy levels: Private, Organizational, and Public.

If you're trying to combine or merge data from two different sources, and their privacy levels conflict (e.g., one is set to 'Private' and the other to 'Organizational'), Power BI's Firewall will evaluate if it's safe. While it does this evaluation, it may buffer a large amount of data from one source before sending a query to the next, causing queries to show as "pending" as they wait for the firewall to clear the data transfer.

4. Query Dependencies and Complex Logic

In more advanced Power BI reports, you might build queries that reference other queries. For example, you might have a base "Sales Data" query and a second query called "Top 10 Products" that references "Sales Data."

In this scenario, the "Top 10 Products" query cannot run until the "Sales Data" query has finished refreshing. If "Sales Data" is a slow, complex query, "Top 10 Products" will display the "pending" icon until its prerequisite is complete.

How to Troubleshoot and Fix the Pending Icon

Now that you know the common causes, here are actionable steps you can take to diagnose and fix the issue.

Step 1: Check if Your Query is Folding

Your first and most important diagnostic step is to see where, or if, your query folding is breaking.

1. In the Power Query Editor, go to your query's "Applied Steps" pane on the right.
2. Click on the last step in your query.
3. Right-click on that step.
4. Look for the option "View Native Query."

If "View Native Query" is enabled (you can click it), your query is successfully folding! If it's grayed out, folding has broken at or before this step. Now you can work backward. Click on the previous step, right-click, and check again. Continue doing this until you find the exact step where "View Native Query" goes from being clickable to grayed out. That's your problem step.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Step 2: Reorder Your Transformation Steps

Once you've identified which step is breaking your fold, try to reorder your steps to be more "folding friendly." The golden rule is to perform transformations that the source can handle first.

Good Practice:

1. Connect to source.
2. Filter Rows (e.g., only show sales from the last year).
3. Remove unneeded columns.
4. Do a calculation that the source understands (e.g., standard math).
5. Then, add your Index Column or apply other complex transformations that break folding.

By filtering early, you dramatically reduce the amount of data Power BI has to pull across the network and process locally after the fold breaks.

Step 3: Check and Align Your Privacy Levels

If you suspect a privacy firewall issue is slowing you down:

1. From the main Power BI window, go to File > Options and settings > Data source settings.
2. In this dialog, you'll see all the data sources used in your current file.
3. Select each one and click "Edit Permissions."
4. In the settings for each source, you'll find a dropdown for "Privacy Level."
5. For combining internal company sources (like two different SQL servers), ensure they are both set to "Organizational." For combining an internal source with a public web source, ensure the website is marked as "Public." Making these consistent can often resolve unexpected buffering and pending states.

Step 4: Communicate With Your IT or Database Admin

Don't be afraid to investigate the source system itself. If your query is folding perfectly but is still slow, the problem is likely not with your Power BI design. Reach out to the owner of the data source. Ask them if the server is under heavy load or if they can monitor the performance of the query you are sending. They may be able to optimize an index on their end that makes your report refresh ten times faster.

Final Thoughts

That "Pending outgoing request" message in Power BI is a sign of a performance bottleneck, most often caused by broken query folding forcing Power BI to process huge amounts of data on your local machine. By understanding what query folding is, identifying the step that breaks it, and reordering your transformations to be more efficient, you can solve the majority of these frustrating delays and get back to building insightful reports.

Wrestling with query performance and spending hours optimizing steps in tools like Power BI is a common friction point for many marketing and sales teams. Instead of needing to become a technical expert, we built Graphed to remove this complexity entirely. Simply connect your data sources - like Google Analytics, Salesforce, or Shopify - and our AI handles building efficient queries for you. You can ask for dashboards and reports in plain English, and Graphed instantly generates live visuals without you ever having to see, let alone troubleshoot, a "pending" icon.