Skip to main content
A Run is one execution of a pipeline (or a slice of it). Runs are scoped to a project and carry per-step status.

​
How runs start

​
What runs

The scope depends on how the run was started:
  • Run all — every root step in the project, cascading to all descendants.
  • Run step — the chosen step and its full downstream subtree. Useful for re-running a failed branch.
  • Schedule / cascade — the ancestor closure of the triggered database step (everything required to refresh that database).
Steps at the same topological level run in parallel.

​
Run statuses

Each step has its own status within a run: pending, running, success, failed, skipped, or cancelled.

​
Where to see them

  • Project page — recent runs for this project, with the latest status per step.
  • Run timeline — drill into a single run to see per-step duration, rows processed, and any error.

​
Cascade events

Some cascades are skipped on purpose—for example, when the upstream database didn’t actually change since the last successful refresh. These show up as cascade events on the project timeline (muted, recent success, no change, race) so you can see “would have re-run but didn’t” without surprise.