Cross-pipeline dependencies

Use pipeline dependency views to understand how pipelines in one project depend on each other.

​

Explore the project graph

Open /apps/pipelines/graph to review the cross-pipeline dependency graph. Each node represents a pipeline. Each edge points from an upstream pipeline to a downstream pipeline:

1. Upstream pipelines must run first or provide data, state, or execution context used by the selected pipeline.
2. Downstream pipelines depend on the selected pipeline or run after it.
3. Selecting a pipeline focuses it and highlights the upstream and downstream paths that match the current trace direction.

The graph is read-only. Update pipeline relationships from the pipeline or dependency configuration surfaces that create the underlying upstream and downstream metadata. When the dependency response includes pipeline colors, the graph uses those colors for the matching pipeline nodes.

​

Focus on one pipeline

Use Find pipeline to search by pipeline name or UUID. Selecting a result centers the graph on that pipeline, selects it, and highlights the dependency paths that match the selected trace direction.

​

Filter the neighborhood

Use the graph controls to narrow large projects:

1. All pipelines shows every pipeline node returned by the dependency source.
2. With dependencies hides isolated pipelines that do not have an upstream or downstream relationship.
3. Both highlights upstream and downstream pipelines around the focused pipeline.
4. Upstream highlights only pipelines that lead into the focused pipeline.
5. Downstream highlights only pipelines that depend on or follow the focused pipeline.

Clear the focus to return to the project-wide graph.

​

Review pipeline relationships

Open a pipeline and select Dependencies to review the pipelines connected to the current pipeline. The page groups relationships into upstream dependencies and downstream pipelines, and shows the relationship type, active trigger count, edge source, and latest run status when Mage can resolve that information. Dependency edges can come from configured relationships, runtime lineage, or pipeline code that calls helpers such as trigger_pipeline, trigger_pipeline_for_workspace, trigger_workspace_pipeline, and check_status. When a pipeline is focused, highlighted graph edges show concise relationship labels such as Trigger, Sensor, and Global data product.

​

Trace dependencies between pipeline runs

Open an individual pipeline run and select Run lineage in the right-side inspector. The inspector initially opens to Dependency tree; Mage requests lineage for only the current run when you select Run lineage. The tab groups the recorded relationship into:

1. Upstream run shows the direct parent run, when one was recorded.
2. Downstream runs shows up to five direct child runs created by the current run.

The summary reports the exact direct relationship totals, such as 1 upstream · 22 downstream. For a related run in the current workspace, its pipeline name, run ID, and status are shown only when you can view that pipeline. When a persisted relationship points to another workspace, the tab shows only a minimal reference containing the persisted pipeline UUID and run ID. It does not include that run’s status, timestamps, duration, schedule, or trigger metadata. The reference links to the related run in its workspace; opening that page uses the destination page’s normal authorization and denies access when you cannot view the target pipeline. Current-workspace runs that you cannot view are not listed as nodes. Instead, the affected group reports an aggregate such as 4 additional downstream runs hidden by permissions. A persisted relationship whose run or schedule is no longer available, or that cannot provide usable workspace navigation context, is also reported only as an unavailable aggregate without exposing its identity. The tab does not paginate. When more related direct children exist, the single dependency action reports how many are not displayed and opens the pipeline’s full dependency page. For an unusually large fan-out that cannot be completely classified by the bounded lineage lookup, the action reports that additional downstream runs exist without estimating permission-hidden or unavailable categories. Use the dependency page to continue exploring the pipeline-level relationship.

​

Runtime lineage versus pipeline dependencies

The Run lineage tab shows direct, persisted runtime trigger relationships between specific runs. Mage records these relationships when supported helpers such as trigger_pipeline, trigger_pipeline_for_workspace, or trigger_workspace_pipeline create a child run. This view does not infer a run relationship from the project graph, recurse through later descendants, or reconstruct relationships for historical runs. The project graph and pipeline Dependencies page describe relationships between pipeline definitions. They can include configured dependencies, sensors, global data products, and other evidence that does not identify a specific parent and child run. Use the graph to understand pipeline-level impact, and use the individual run view when you need the recorded execution-level provenance. Runs started by ordinary schedules or events, direct run creation, external orchestrators, and older executions without a persisted runtime trigger edge do not gain inferred lineage in this view. When no direct persisted relationship exists, the tab reports that no upstream or downstream runs were recorded for the run.

​

Use diagnostics

The graph reports diagnostics when dependency metadata is incomplete or ambiguous, such as a pipeline referencing a missing pipeline, a self-dependency, or a cycle. Use diagnostics to decide whether the project needs dependency metadata cleanup before relying on the graph for release planning or incident analysis.

​

Validate relationship direction

When reviewing a dependency layout, confirm the selected pipeline context before acting:

1. Select the pipeline you care about.
2. Check whether the highlighted relationships point upstream or downstream from the selected pipeline.
3. Use Upstream to highlight the pipelines that must run before the selected pipeline.
4. Use Downstream to highlight the pipelines that can be affected by the selected pipeline.
5. Follow the highlighted edge labels to confirm which dependency evidence Mage resolved for each relationship.

For dense graphs, keep the focused pipeline selected and move between direction filters instead of trying to interpret every edge at once.

​

Cancel downstream runs

When cancelling a running pipeline run, Mage can also cancel downstream runs that were triggered by that run. In the cancellation confirmation, select Cancel downstream runs triggered by this run to preview the eligible downstream runs before confirming. The preview only counts downstream runs that are still running or queued and that you have permission to cancel. Runs that are already terminal are skipped, and runs you cannot edit are shown as blocked. Leaving the option unchecked cancels only the selected pipeline run.