Skip to main content
When a run fails, retry it from the Run Details page instead of rebuilding commands or starting a new schedule. Choose how much to re-execute; a new run is created and the original is never modified.

Retry modes

Infrastructure commands (git clone, dbt deps) always run automatically on every Bolt run, so they are not retried.

Retry from the UI

  1. Open the failed run from a schedule’s run history.
  2. On the Run Details page, click Retry.
  3. Choose a mode: Retry from failure (default) or Retry all commands.
  4. Confirm. A new run is queued immediately.
The new run appears in the run history with its own run ID and links back to the original.

What happens to the original run

  • The original run’s status, logs, artifacts, and timeline are unchanged.
  • The retry is a separate entry with its own run ID, start time, and logs.
  • Each retry creates its own new run. Retries do not chain; they all reference the original failed run.
  • Notifications (Slack, email, Microsoft Teams) fire on the new run like any other Bolt run.

Retry from code

The same retry behaviour is available from the CLI, SDK, and API, for automating retries from CI or an incident-response tool: