Skip to main content
August 12, 2026
A Bolt run graph where dbt run and dbt test fail but the pipeline continues to dbt debug
Until now, a failed command skipped everything after it. Bolt schedules now take a Continue on error toggle, plus a per-command override (Default, Continue, or Stop) on every command row, so a failing test no longer has to block the rest of the pipeline. The run is still reported as failed, and retries preserve the per-command settings. The same options are available everywhere schedules are defined: the schedule form, paradime_schedules.yml, and the GraphQL API via commandConfigs on createBoltSchedule and triggerBoltRun. Shipped in Paradime v6.6.0, with paradime schedule verify and in-app YAML editing support in v6.6.1.

Related topics

ChangelogCommandsBolt APIDebugging Failed RunsBolt