Skip to main content
Version: 10.3

Asset Lineage Is Incorrect (End-Event Triggers)

Symptoms​

You may encounter downstream assets that never start after upstream asset completion.

System Behavior​

Dagster establishes lineage relationships by matching configured asset references against existing asset definitions during asset discovery and workspace loading.

For end-event triggers:

  • The job-name field is treated as a reference to another asset.
  • Dagster validates whether the referenced asset exists.
  • Only valid and existing asset names are eligible for lineage creation.
  • If no matching asset is found, the lineage relationship is ignored.

Because lineage validation only accepts existing asset definitions, incorrectly referenced asset names prevent downstream dependencies from being registered.

Possible Causes​

This issue may occur because the job-name value does not exactly match an existing asset name.

Resolution​

Follow these steps to resolve the issue:

  1. Open the asset configuration files for the affected workflow.
  2. Identify the configured job-name value used in the end-event trigger.
  3. Verify that the referenced asset exists in the Dagster workspace.
  4. Make sure that the job-name value matches the target asset’s asset field.