Skip to main content
Open a run from a schedule’s run history to see what happened: the pipeline, the executed nodes, timing, and per-command logs.

Overview

The header shows the run number, its status, and when it ran. A metadata row shows the date, duration, trigger, owner, branch and commit, SLA, and self-healing. The stats panel shows the Succeeded, Errors, and Skipped counts.

Run views

Switch between three views of the run:
  • Pipeline — the commands as a DAG, each with its status.
  • Executed nodes — the individual dbt™ objects (models, tests, and so on) the run built.
  • Model timeline — models over time, to spot long-running or bottleneck models.

Retry

If a run fails, click Retry to resume from the failed command or re-run every command. Each retry creates a new run and leaves the original intact. See Retrying a run.

Logs and artifacts

Each command in the run has an AI summary, full logs, and downloadable artifacts. See Run logs and artifacts.