Commands - Paradime

After configuring the Triggers and Schedule settings of a Bolt schedule, you add the commands the schedule runs. Commands run in order, so you can chain a full pipeline: sync sources, run dbt™ transformations, run data quality checks, then refresh dashboards. To add a command, open a schedule, click Add command, and pick a command type from the categories below. Each command type has its own modal: some expose structured fields, others accept any command the underlying Paradime CLI supports.

Commands execution logic

Paradime follows a specific execution logic to handle errors and decide whether later commands run:

Command completes with an error: by default, the remaining commands in the schedule are skipped. Use Continue on error to change this.
Exceptions that still run after an error:
- Source freshness and source status: if a dbt source freshness command errors and the next command uses the source_status:fresher selector, the next command still runs.
- Elementary: an Elementary command runs regardless of a previous error, so you can send alerts and generate reports on test failures.
- Monte Carlo: a Monte Carlo command runs regardless of a previous error, so dbt™ artifacts are always uploaded.

Continue on error

You can override the default skip behavior at two levels in the Commands section of the schedule form:

Schedule level: turn on the Continue on error toggle to keep running the remaining commands when one fails. The run is still reported as failed.
Per command: each command row has a select with three options: Default (inherit the schedule-level setting), Continue (keep going even if this command fails), or Stop (skip the remaining commands if this command fails).

Per-command settings override the schedule-level toggle, so you can, for example, continue past a failing dbt test while still stopping the pipeline if dbt run fails.