Tableau Desktop takes ~60 seconds to open a Published Data Source (live or extract)
Web authoring on Tableau Server is fast — unaffected
Issue reproduces across all Desktop client machines, including Desktop installed on the same machine as Tableau Server
Local copy of the Published Data Source opens normally in Desktop
Data Server and Hyper logs show healthy response times (dataserver/create.xml completes in ~1s)
Tableau Desktop log.txt shows two sequential GraphQL calls, each blocking for ~30 seconds
Desktop log pattern:
POST /relationship-service-war/graphql -> 200, 119 bytes, 30.29 s
POST /relationship-service-war/graphql -> 200, 119 bytes, 30.95 s
GraphQLHelper::GetData error: (empty error string)
httpd access log shows 100% failure rate on all three Metadata API endpoints:
| Endpoint | Median duration | Response |
/api/metadata/graphql | ~30.6 s | HTTP 200, 119 bytes |
/api/exp/metadata/graphql | ~30.9 s | HTTP 200, 119 bytes |
/relationship-service-war/graphql | ~30.7 s | HTTP 200, 119 bytes |
Perform a full metadata services re-ingestion:
tsm maintenance metadata-services get-status
tsm maintenance metadata-services disable
tsm stop
tsm start
tsm maintenance metadata-services enable
tsm maintenance metadata-services get-status
After re-enabling, monitor the ingestion progress using the Backfill API. For environments with ~60 Creators / ~700 Viewers, re-ingestion typically completes in under 2 hours.
This issue is expected to affect any Tableau Server 2025.3.x deployment where metadata services did not complete ingestion successfully after the upgrade
A full restart (tsm stop / tsm start) before re-enabling metadata services is recommended to ensure a clean NIMC initialisation
There is no client-side workaround to skip or make the metadata GraphQL calls asynchronous — the fix must be applied server-side
For the duration of the outage, users can work around the slowness by creating a local copy of the Published Data Source in Tableau Desktop (right-click the data source → Create Local Copy)
005389446

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.