Power Query Download Not Complete: Network Timeout Fix in 3 Steps

Why it happens

When your Power Query download stalls or fails to complete, it’s rarely due to a single, obvious issue. Instead, a mix of technical hiccups—often tied to your system, network, or data source—can derail the process.

Below, we break down the most frequent causes, explained in plain terms with actionable insights to help you diagnose the problem.

###

🔌 Network Instability or Throttling

Power Query relies on a stable, high-speed connection to fetch data from online sources (like APIs, web tables, or databases). If your network is acting up, the download may time out before completion. Here’s why:

• Latency spikes: High ping times (delay in data transmission) can cause the query to exceed its default timeout threshold (often 30–60 seconds). This is common on Wi-Fi networks or when your ISP is under heavy load.
• Bandwidth limits: Corporate firewalls or ISPs may throttle background traffic, slowing down data retrieval. Power Query’s lightweight requests can get caught in this crossfire.
• Proxy or VPN issues: If you’re behind a proxy server or VPN, encryption overhead or misconfigured settings can disrupt the connection mid-download.

Pro tip: 🔥 Test your network speed using Speedtest. If speeds are inconsistent, try switching to a wired connection or disabling VPNs temporarily.

###

📊 Server-Side Timeouts or Rate Limits

Not all data sources are created equal. Some servers enforce strict timeout policies or rate limits, which can abruptly terminate your Power Query session. Here’s how it plays out:

• Server timeouts: Web APIs or databases may close idle connections after 20–60 seconds of inactivity. If Power Query takes longer to process a large dataset, the server may drop the request before completion.
• Rate limiting: Free-tier APIs (e.g., Google Sheets, public datasets) often cap requests per minute. Exceeding this limit triggers a 429 "Too Many Requests" error, which Power Query may misinterpret as a failed download.
• SSL/TLS handshake failures: Outdated security protocols or self-signed certificates can stall the connection, causing Power Query to hang indefinitely.

Pro tip: 🌡️ Check the data source’s documentation for timeout or rate-limit policies. For APIs, use tools like Postman to test endpoints manually before reprocessing in Power Query.

###

🖥️ System Resource Constraints

Power Query runs in the background, competing for your computer’s CPU, RAM, and disk I/O. If your system is overwhelmed, the query may stall or fail silently. Key triggers include:

• Low memory (RAM): Large datasets or multiple simultaneous queries can exhaust RAM, causing Power Query to freeze. Windows may even kill the process to "protect" your system.
• Disk I/O bottlenecks: If your storage drive is slow (e.g., HDD vs. SSD) or overloaded by other tasks, temporary files used during query processing may not write correctly, leading to incomplete downloads.
• Background processes: Antivirus scans, updates, or other apps hogging resources can interrupt Power Query’s data pipeline.

Pro tip: ✨ Open Task Manager (Ctrl+Shift+Esc) and monitor Memory and Disk tabs while running the query. If usage spikes to 90%+, close unnecessary programs or restart your PC.

###

🔗 Corrupted or Misconfigured Data Sources

Sometimes, the issue isn’t your network or system—it’s the data itself. Power Query may fail to complete if the source is malformed or misconfigured:

• Broken URLs or endpoints: A typo in the API URL or a dead link can cause Power Query to loop endlessly or return a 404 error.
• Unsupported file formats: While Power Query handles CSV, JSON, and Excel well, niche formats (e.g., proprietary databases) may trigger parsing errors.
• Authentication failures: Expired tokens, incorrect credentials, or missing headers in API requests can block access mid-download.

Pro tip: 🎯 Validate your data source manually. For APIs, use Web.Contents() in Power Query’s Advanced Editor to test connectivity step-by-step.

How to solve it

When your Power Query download stalls mid-execution, it’s usually a mix of network hiccups, data overload, or software quirks. Below are practical, step-by-step solutions tailored to common causes—plus tips to keep your queries running smoothly. No jargon, just fixes.

🔥 1. Network or Server Issues: Restart & Retry

If the download freezes due to slow connections or server timeouts, these tweaks can reset the process:

🔄 Restart Power Query & Refresh

• Close and reopen Excel (or Power BI/your tool). Sometimes, a simple restart clears temporary glitches.
• Restart your router (unplug for 30 seconds, then plug back in). This refreshes your network connection.
• Try downloading the data again immediately—many timeouts resolve after a brief network reset.

📶 Switch to a Wired Connection

Wi-Fi can be unstable. If possible:

• Plug your device directly into an Ethernet cable for a stable, high-speed connection.
• If Wi-Fi is your only option, move closer to the router or use a 5GHz band (less interference than 2.4GHz).

💡 Prevention Tip:

For large datasets, schedule downloads during off-peak hours (e.g., late at night) when network traffic is lighter. Use Power Query’s "Load to Data Model" instead of loading all data at once to reduce strain.

🍳 2. Data Source Overload: Trim & Optimize

If the query is stuck because the source is too heavy (e.g., a massive CSV or API response), these adjustments can help:

📉 Reduce Data Volume

• Use Power Query’s "Keep Rows" filter to load only the columns you need (e.g., exclude unused fields).
• For APIs, limit records per request (e.g., fetch 1,000 rows at a time instead of 10,000).
• If working with Excel files, convert to a lighter format (e.g., CSV instead of XLSX) before importing.

🔄 Split Large Queries

Break the download into smaller chunks:

• Use "Append Queries" to combine results after downloading in batches.
• For web data, paginate manually (e.g., download pages 1–5 first, then 6–10).

⏰ Prevention Tip:

Enable "Enable Fast Combine" in Power Query’s Options → Data Load to speed up merges. For APIs, check if the source supports compression (e.g., gzip)—this can cut download times by 50%.

👨‍🍳 3. Software Glitches: Reset & Update

Sometimes, the issue lies in Power Query itself. Try these fixes:

🔄 Clear Power Query Cache

Corrupted cache files can cause freezes:

• Close Excel/Power BI.
• Delete the cache folder:
  • Windows: %LocalAppData%\Microsoft\Power Query Cache
  • Mac: ~/Library/Caches/Microsoft/Power Query Cache
• Restart your tool and re-run the query.

🔧 Update Power Query & Drivers

• Update Excel/Power BI to the latest version (go to File → Account → Update Options).
• If using ODBC or SQL drivers, update them via the manufacturer’s website (e.g., Microsoft ODBC Driver for SQL Server).

💡 Prevention Tip:

Enable "Automatic Updates" in your tool’s settings to avoid compatibility issues. For enterprise users, test queries on a secondary machine to isolate whether the problem is environment-specific.

🥘 4. Firewall/Antivirus Blocking: Whitelist Power Query

Security software can mistakenly block Power Query’s network requests:

🛡️ Temporarily Disable Firewall/Antivirus

• Pause your firewall (Windows Defender, McAfee, etc.) for 2 minutes and retry the download.
• If it works, add an exception for:
  • msquery.exe (Excel’s Power Query process)
  • Your Excel/Power BI application

🔒 Prevention Tip:

Create a dedicated Windows user profile for data tasks with minimal security restrictions. This isolates potential conflicts without risking your main account.

⏰ 5. Timeout Settings: Adjust for Slow Sources

If the source server is slow to respond, Power Query’s default timeout may be too short:

🕒 Increase Timeout in Power Query

For web sources (e.g., APIs):

• In the Advanced Editor, add this line after let:

  Source = Web.Contents("https://example.com", [ManualStatusHandling={404,500}, Timeout=#duration(0,0,0,30)]),

  (Increases timeout to 30 seconds—adjust as needed.)
• For SQL sources, check your connection string for a ConnectTimeout parameter.

⚡ Prevention Tip:

Use Power Query’s "Retry" function for flaky connections. Add this to your query:

= Web.Contents(url, [RetryCount=3, RetryDelay=#duration(0,0,2)])

Frequently asked questions