What causes ExplorerLineageUnavailable?

No production dbt Cloud job has successfully completed and uploaded artifacts for the project. The dbt Cloud project is not configured with a production environment, so Explorer has no manifest to display. A recent artifact upload failure left Explorer pointing at a stale or incomplete manifest. The project is on a dbt Core plan without dbt Cloud Explorer access

How do I fix ExplorerLineageUnavailable?

Step 1: In dbt Cloud, verify the project has a production environment configured under Deploy > Environments.. Step 2: Check that the most recent production job run completed successfully and uploaded artifacts.. Step 3: If artifact upload failed, re-run the production job to generate and upload a fresh manifest.. Step 4: In dbt Explorer, click 'Render Lineage' or refresh the page — large projects may take time to render.. Step 5: For multi-project Mesh setups, verify all upstream projects have recent successful runs with uploaded artifacts.

Low severityconfiguration

Power BI Refresh Error:
ExplorerLineageUnavailable

What does this error mean?

The dbt Explorer lineage graph is not rendering or shows stale data because the production environment has not successfully uploaded a recent manifest artifact, or the project is not connected to a production environment.

Common causes

1No production dbt Cloud job has successfully completed and uploaded artifacts for the project
2The dbt Cloud project is not configured with a production environment, so Explorer has no manifest to display
3A recent artifact upload failure left Explorer pointing at a stale or incomplete manifest
4The project is on a dbt Core plan without dbt Cloud Explorer access

How to fix it

1Step 1: In dbt Cloud, verify the project has a production environment configured under Deploy > Environments.
2Step 2: Check that the most recent production job run completed successfully and uploaded artifacts.
3Step 3: If artifact upload failed, re-run the production job to generate and upload a fresh manifest.
4Step 4: In dbt Explorer, click 'Render Lineage' or refresh the page — large projects may take time to render.
5Step 5: For multi-project Mesh setups, verify all upstream projects have recent successful runs with uploaded artifacts.

Frequently asked questions

How often does dbt Explorer refresh its lineage graph?

dbt Explorer refreshes its graph after each successful production job run that uploads a new manifest.json artifact. It does not poll continuously — the refresh is triggered by a successful artifact upload event.

Can I see historical lineage in dbt Explorer?

dbt Explorer shows the lineage from the most recently uploaded manifest. It does not provide a historical timeline view of how lineage changed over time. For lineage history, consult your version control system or dbt Cloud run history.