Loading

Tableau Cloud – Data Catalog lineage or metadata shows outdated information after content is changed or republished

Publiseringsdato: Jul 9, 2026
Beskrivelse

After making a change to content in Tableau Cloud, the Data Catalog Lineage tab (or the Metadata API results) continues to show outdated information rather than reflecting the change. Common examples include:

  • A published data source, workbook, or flow that was re-pointed to a different upstream source, but lineage still shows the previous (old) source.
  • A Prep flow whose input was swapped and re-run, but lineage still lists the pre-change input.
  • A renamed, moved, or re-published asset whose lineage, description, or certification still reflects its former state.
  • Newly added upstream databases, tables, or columns that have not yet appeared in lineage.

In these cases the lineage itself renders correctly, it is simply stale, it reflects the content as it was before the change. This happens because Data Catalog lineage and metadata are refreshed by a background ingestion process rather than in real time, so a change is not reflected the moment it is made.

Løsning

In most cases this resolves on its own, no action is required beyond waiting for the next ingestion cycle. Work through the steps below in order.

Step 1 — Confirm the change fully completed on the source content

A change is only picked up for lineage once the underlying operation has fully and successfully completed.

  1. Confirm the change was saved/published successfully (for a data source or workbook, that it republished without error).
  2. For a Prep flow, confirm the most recent run after the change completed successfully with no errors. A flow input change is only ingested after a successful run. If the run failed, resolve it and re-run before continuing.
  3. For an extract-backed source, confirm the extract refresh completed successfully.

Step 2 — Allow the background ingestion cycle to complete

Data Catalog lineage and metadata update asynchronously, not in real time. After a change there is a normal lag before the Lineage tab and Metadata API reflect it.

  1. Allow time for the next ingestion cycle to complete. This is typically a few hours, but can take up to a few days depending on current processing volume on your Cloud pod. There is no fixed SLA for ingestion timing.
  2. Re-check the Lineage tab (or re-run your Metadata API query) for the affected content. In most cases it will now show the correct, current information.

Step 3 — Optionally force a fresh re-ingestion (tag add/remove)

This step is optional and only speeds things along, it is not required, as the normal ingestion cycle will pick the change up on its own. Adding then removing a tag queues a fresh re-ingestion event for that specific content.

  1. In Tableau Cloud, navigate to the affected content (data source, workbook, or flow).
  2. Add any tag to the item and save it (any tag name is fine).
  3. Remove that same tag.
  4. Note the exact date and time (including time zone) you did this, in case further investigation is needed.
  5. Allow the next ingestion cycle to complete (again, up to a few days) and re-check the lineage.
Knowledge-artikkelnummer

005388760

 
Laster
Salesforce Help | Article