Skip to main content
October 29, 2026 Cancelling a Bolt run used to stop the run’s pod at once. dbt™ never got the signal, so the queries it had sent kept running in the warehouse: BigQuery jobs were orphaned and Snowflake queries ran to completion, still using compute you were paying for. Now a cancel gives dbt™ up to 60 seconds to cancel its in-flight queries first. It uses dbt™‘s own cancel, so it works on any adapter that supports it. On BigQuery, that means dbt-bigquery 1.9 or later. It applies however you cancel: from the UI, the API, or when Turbo CI cancels an older run.
  • The run shows Canceled at once.
  • The next command in the schedule doesn’t start.
  • Non-dbt™ commands stop at once, as before.
  • A cancelled run sends no notifications and starts no downstream schedules.
See Cancel a run. Shipped with the October 26 platform release.