Why Is My Tableau Extract Not Refreshing?

Few things in data analysis are more frustrating than a Tableau dashboard that isn't showing the latest data. You’ve built the perfect visualization, your team relies on it, but when you check it in the morning, you're still looking at yesterday's numbers. If your Tableau extract isn’t refreshing automatically, you're not just dealing with an inconvenience, you're dealing with stale information that can lead to poor decisions. This article will walk you through the most common reasons why Tableau extracts fail to refresh and provide a clear, step-by-step guide to get your data flowing again.

Graphed

Your AI Data Analyst to Create Live Dashboards

Connect your data sources and let AI build beautiful, real-time dashboards for you in seconds.

Build Your First Dashboard

Understanding Your Connection: Live vs. Extract

Before diving into troubleshooting, it's essential to confirm you're actually using a Tableau Extract. Tableau connects to data in two ways: through a Live connection or an Extract.

• A Live connection queries the source database or file directly. Every time a user interacts with your dashboard (like applying a filter), Tableau sends a new query. You see the data in real-time, but this can be slow if the underlying database is massive or busy.
• An Extract (.hyper or formerly .tde) is a snapshot of your data. The data is pulled from the source and stored in a highly compressed, optimized file. Dashboards connected to extracts are usually much faster, as Tableau is querying a local, performance-tuned file instead of a remote database. The catch? The data is only as fresh as your last refresh.

A "refresh" only applies to extracts. If you are on a live connection, your data is, by definition, live. Here's how to check which connection type you're using in Tableau Desktop:

1. In your workbook, look at the Data pane on the left side.
2. Right-click on your data source.
3. Observe the menu:

If you've confirmed you're using an extract and it's not refreshing, an issue is happening somewhere in the pipeline between Tableau and your data source.

Common Refresh Issues in Tableau Desktop

Troubleshooting starts right where you build: in Tableau Desktop. If you can't manually refresh the extract on your local machine, it definitely won't work on a server schedule.

Incorrect File Path or Database Credentials

This is the most common culprit. The breadcrumbs Tableau followed to find your data are now broken.

• The Problem: For file-based data sources like Excel or CSVs, the file may have been moved, renamed, or deleted. For databases, credentials like a password may have changed, or the server/host address is no longer correct.
• The Fix:

Pro-Tip: When connecting to a file on a shared network drive, always use a Universal Naming Convention (UNC) path (e.g., \\server\share\data.xlsx) instead of a mapped drive letter (e.g., Z:\data.xlsx). This ensures the path is absolute and consistent for you, a colleague, or the Tableau Server.

AI for Data Analysis

Crash Course

Graphed

Free PDF Guide

AI for Data Analysis Crash Course

Learn how to get AI to do data analysis for you — the best tools, prompts, and workflows to go from raw data to insights without writing a single line of code.

Download Free Guide

The Source File in Use

This one often stumps new users because of its deceptive simplicity.

• The Problem: Tableau can't refresh an extract if the source file is open. This applies primarily to Microsoft Excel files. If you or a coworker have the source spreadsheet open, Excel places a lock on the file, preventing other programs from accessing and reading it.
• The Fix: Ensure the source file (e.g., the Excel sheet) is closed on all computers. Then, try the refresh again in Tableau Desktop.

Decoding Refresh Failures on Tableau Server & Cloud

When you've automated a refresh using a schedule on Tableau Server or Tableau Cloud, a new set of variables comes into play. You have to think from the server's point of view, not your own computer's.

Embedded Credentials Problem

Your manual refresh works on Tableau Desktop because it's using your cached credentials. The server, however, needs its own set.

• The Problem: For an automated refresh to work, the data source’s database credentials must be embedded into the connection on the server. If they aren't embedded, the server has no password to use and cannot log into the database. Often, passwords expire as part of corporate security policies, causing a previously successful refresh to suddenly start failing.
• The Fix:

Missing or Mismatched Database Drivers

The server needs to speak the same language as your database. Database drivers are the translators.

• The Problem: Tableau Server does not come pre-installed with drivers for every possible data source. If you're trying to connect to a PostgreSQL database, for example, the PostgreSQL driver must be installed on the machine running the refresh task (the "Backgrounder" node). A missing, corrupted, or outdated driver will result in an immediate connection failure.
• The Fix: This one is for your Tableau Server Administrator. They must log into the server machine(s) responsible for running refreshes and install the correct 64-bit drivers from the official Tableau Drivers page. For multi-server installations, the driver has to be installed on every single node that runs a Backgrounder process.

Graphed

Your AI Data Analyst to Create Live Dashboards

Connect your data sources and let AI build beautiful, real-time dashboards for you in seconds.

Build Your First Dashboard

Network Firewalls & Accessibility

Just because your computer can see the data source doesn't mean the server can.

• The Problem: Tableau Server (often residing in a data center or on a specific VLAN) may not have a network path to your data. Firewall rules could be blocking communication between the server and your database on the required port. For file-based sources, this circles back to the UNC path issue, the server's "Run As User" account must have permissions to access that network share.
• The Fix:

Extract Refresh Timeout or Overload

Sometimes, the connection works, but the process simply takes too long.

• The Problem: By default, Tableau Server allows a refresh extract task to run for a maximum of 2 hours (7200 seconds). If your query is incredibly complex or the database is under heavy load, the refresh can time out before it finishes. Alternatively, your server may simply be overloaded, with too many refreshes scheduled at the same time and not enough "Backgrounder" resources to handle them all.
• The Fix:

Your Go-To Checklist for a Failed Extract

When an extract fails, don't panic. Go through this systematic diagnostic routine:

1. Check the Alert: Start with the notification email from Tableau. It often contains a specific error message that points you directly to the cause, such as "Invalid username or password" or "Timeout occurred." This is your best opening clue.
2. Test the Connection in Tableau Server/Cloud: Navigate to the data source and use the "Test Connection" button mentioned earlier. If it fails, that confirms the problem is with credentials or network accessibility.
3. Run the Refresh Manually on the Server: On the "Extract Refreshes" tab for the data or workbook, click the ellipsis ... and select Run Now. Does it fail instantly? It's likely a connection, driver, or permissions issue. Does it run for a while and then fail? Looks more like a timeout.
4. Refresh on Tableau Desktop: Download a fresh copy of the workbook from the server and try refreshing it there.

Final Thoughts

Troubleshooting extract refresh issues often involves a mix of simple fixes, like ensuring the file path is correct, and server-side configurations such as drivers and permissions. Following a systematic checklist - check the alert, test the connection, refresh manually, isolate Desktop vs. Server - is the fastest way to pinpoint the exact failure point and resolve it before stale data affects business decisions.