Running pipelines¶

astro run executes registered pipeline steps on an ingested run.

Basic usage¶

astro run
astro run --run-id abc12
astro run --mode cli

Run resolution¶

When --run-id is omitted, Astro selects a run in this order:

Latest quarantined run
Latest failed run with quarantined steps
Latest ingested run

Display modes¶

Mode	Description
`dashboard` (default)	Rich three-panel UI: steps (left), live log (right), status bar (bottom)
`cli`	Plain console log output (still written to the run log file)

Step execution¶

By default, run steps execute serially in registration order, respecting depends_on.

When step_execution_mode = StepExecutionMode.PARALLEL, Astro dispatches ready steps to a thread pool. A step runs when all dependencies are complete, up to max_parallel_workers at a time.

Run outcomes¶

Outcome	Meaning
`completed`	All steps finished with no quarantined rows
`quarantined`	Some steps quarantined rows; run is retryable
`failed`	Hard error or dependency block stopped the run

astro run appends logs to .working/{run_id}/astro.log with session separators between invocations.

View pipeline flow¶

astro describe

Prints a terminal flow diagram of ingest and run steps.

Retry quarantined runs¶

Re-run astro run against a quarantined run (or a failed run with quarantined steps). See Row quarantine for retry behaviour.

Next steps¶

Steps and file I/O — implement step functions
CLI reference — full CLI reference