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

How to solve it

When your Power Query download hangs or fails to complete, it’s usually a mix of network issues, file size limits, or configuration quirks. Below are practical, step-by-step fixes tailored to the most common causes—plus tips to keep your queries running smoothly.

###

🔥 1. Network Timeout or Slow Connection

If your query is stuck due to a network timeout, try these quick fixes:

• ⏰ Increase the timeout setting:
  1. Open Power Query Editor.
  2. Go to File > Options > Query Options.
  3. Under Global, set Command Timeout (seconds) to 120-300 (default is often too low).
  4. Click OK and retry.
• 📶 Switch to a faster network: If on Wi-Fi, try Ethernet or a mobile hotspot with stronger signal.
• 🔄 Restart your router/modem: Sometimes a simple reboot clears latency issues.

💡 Prevention tip: Schedule large downloads during off-peak hours to avoid congestion.

###

🍳 2. File Too Large or Corrupted

Oversized or damaged files can freeze Power Query. Here’s how to handle them:

• 📁 Split the file:
  1. Use Excel’s Text to Columns (for CSV) or Power Query’s "Split Column" to break the file into smaller chunks.
  2. Load each chunk separately, then Append Queries in Power Query.
• 🔍 Check for corruption:
  1. Open the file in a text editor (like Notepad++) to scan for garbled characters or unexpected line breaks.
  2. If corrupted, try re-downloading or request a clean copy from the source.
• 📊 Use a lighter format: Convert to CSV or Parquet (smaller file sizes) if working with Excel.

💡 Prevention tip: Validate file integrity before importing—use =FILE.TYPE() in Power Query to check file health.

###

👨‍🍳 3. Power Query Cache or Memory Issues

If Power Query is stuck processing due to cache or memory limits:

• 🧹 Clear the cache:
  1. Close Excel.
  2. Delete the Power Query cache folder:
     • Windows: %LocalAppData%\Microsoft\Power Query Cache
     • Mac: ~/Library/Microsoft/Power Query Cache
  3. Restart Excel and reload your query.
• 🖥️ Free up RAM:
  1. Close other heavy applications (e.g., browsers, video editors).
  2. Restart your PC to clear temporary memory leaks.
• ⚙️ Reduce query complexity:
  1. Simplify steps—remove unnecessary Merges or Group By operations.
  2. Use Query Folding (check the Advanced Editor to ensure steps are pushed to the source).

💡 Prevention tip: Set a refresh schedule for large queries to avoid overloading Excel during peak usage.

###

🥘 4. Source Server or API Limits

If the issue stems from the data source (e.g., SQL Server, SharePoint, or API):

• 🔑 Check API rate limits:
  1. Review the API documentation for request limits (e.g., 100 calls/minute).
  2. Add delays in Power Query using Duration.Days(0) between calls.
• 🔄 Retry with exponential backoff:
  1. Wrap your query in a custom function with retry logic:

  
          let
              RetryQuery = () => try Web.Contents("https://api.example.com/data") otherwise null,
              Result = RetryQuery()
          in
              Result
          

• 📤 Contact the source admin: Ask if the server is throttling requests or if there’s a known outage.

💡 Prevention tip: Use Power Query’s "Keep Errors" option to log failed attempts for debugging.

###

⏰ 5. Excel or Power Query Version Glitches

Bugs in older versions can cause hangs. Try these fixes:

• 🔄 Update Excel/Power Query:
  1. Go to File > Account > Update Options > Update Now.
  2. Restart Excel after updates.
• 🧹 Repair Office installation:
  1. Open Control Panel > Programs > Programs and Features.
  2. Select Microsoft 365 > Change > Quick Repair.
• 📄 Test in a new workbook: Create a blank file and re-import the data to rule out corruption in the original file.

💡 Prevention tip: Enable automatic updates for Office to avoid future compatibility issues.

Most Power Query download failures resolve with one of these fixes. If the problem persists, check Excel’s Trust Center settings to ensure macros and data connections aren’t blocked. For recurring issues, consider optimizing your query steps or switching to a more robust ETL tool like Power BI for large datasets.

Frequently asked questions