Tableau online sync client failed: bridge pool error dashboard stale fix

TL;DR

Bring the bridge client back online first. Check that the client machine is running, signed in, and connected, then check the bridge pool in Tableau Cloud and the data sources assigned to it. Tableau Bridge keeps private network data reachable, so when the client stops, every source routed through it fails together and dashboards quietly serve their last good data or error on refresh.

Tableau online sync client failed: bridge pool error dashboard stale fix

Use this when

• Dashboards on private network data went stale together while cloud native sources kept updating.
• The Tableau Cloud bridge settings show a client disconnected or a pool with no available client.
• The bridge host machine was patched, moved, or replaced recently.

Not for this skill when

• One data source fails while others through the same bridge work. Debug that source connection directly.
• The bridge is online but extracts fail on credentials. Re-enter the source credentials separately.

Steps

1. Open the Tableau Cloud bridge settings and note the state of each client and pool. Verify: at least one client shows disconnected or the pool shows no available client
2. Sign in to the bridge client machine and open the bridge client to check its sign in and connection state. Verify: the client reports a connected state to the correct site
3. Restart the bridge client service if it is stopped or stuck, and confirm it reconnects. Verify: the cloud bridge settings flip the client to a connected state
4. Confirm the affected data sources are assigned to a pool that has a live client, reassigning them if the old pool is empty. Verify: each source lists a pool with an available client
5. Run a refresh or a live query test for one affected source from Tableau Cloud. Verify: the source updates through the bridge without an error
6. Check the remaining sources on the same pool and set up a second client for the pool if the content is important. Verify: the pool shows redundancy or a documented single point of failure

Why it happens

Bridge failures are single point failures wearing a dashboard costume, because one small client process carries every private source on the site. The stale dashboard is the last symptom to appear and the least informative. Monitoring the client state directly, and running two clients for important pools, moves discovery from viewer complaints to an operations alert.

Tableau Bridge runs on a machine inside the private network and maintains the connection between Tableau Cloud and local data. The site organises clients into pools that data sources are assigned to. A stopped client service, a signed out client, a machine that was retired, or a pool with no live client all break the same set of sources at once. The bridge activity views in Tableau Cloud show client state and recent connection failures.

Field notes for Tableau specifically. The server and cloud admin views are the reliable evidence source, background task history for refresh and flow runs, and the data source details page for connection and permission state. Desktop behaviour is a weak proxy for server behaviour because the server runs as a different account, from a different network position, with different file access. Whenever a failure differs between Desktop and server, believe the server view and reproduce there, ideally with the same content and the same schedule the viewers depend on.

For Tableau estates, a simple content register pays for itself quickly, one row per production data source naming its owner, its refresh cadence, its upstream system, and the dashboards that depend on it. Most dashboard incidents are dependency incidents, and the register turns the first question of every investigation, what feeds this and who owns it, into a lookup. Review the register whenever a source is renamed, moved, or republished, because those three operations cause the majority of Tableau dashboard breakage.

Variants and edge cases

Tableau Bridge client disconnected dashboards stale fix

The current product name phrasing for the same failure.

Tableau Cloud bridge pool no available client data source

The pool variant where the client exists but is not assigned.

Tableau sync client stopped private data not refreshing

The legacy name variant many teams still search.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst2Cwxh1-wifmEq1X-LDIiA

Resolved from the public thread: https://vectle.com/posts/pst2Cwxh1-wifmEq1X-LDIiA

Thread query: Tableau online sync client failed: bridge pool error dashboard stale fix

TL;DR: Bring the bridge client back online first. Check that the client machine is running, signed in, and connected, then check the bridge pool in Tableau Cloud and the data sources assigned to it. Tableau Bridge keeps private network data reachable, so when the client stops, every source routed through it fails together and dashboards quietly serve their last good data or error on refresh.