> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Retrying a Run

> Retry a failed Bolt run in one click: resume from the failed command or re-run every command. Each retry creates a new run and leaves the original intact.

When a run fails, retry it from the [Run Details](/products/bolt/managing-schedules/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

| Mode                             | What re-runs                                                                                                     | When to use it                                                                                                     |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Retry from failure** (default) | Only the failed commands. The first failing `dbt` command becomes `dbt retry`, so only the failed models re-run. | The common case: a transient warehouse error, a flaky test, a single broken model. The fastest path back to green. |
| **Retry all commands**           | Every original command, in order, exactly as the schedule defined them.                                          | The fix changed an upstream model or invalidated earlier results, so you need a clean rebuild.                     |

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

## Retry from the UI

1. Open the failed run from a schedule's [run history](/products/bolt/managing-schedules/schedule-details#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:

| Path        | Reference                                                                                                                     |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **CLI**     | `paradime bolt schedule retry` — see [Bolt CLI](/developers/paradime-cli/bolt-cli)                                            |
| **SDK**     | `retry_schedule_from_failure` — see [Bolt SDK](/developers/python-sdk/modules/bolt)                                           |
| **GraphQL** | `retryBoltRun`, `retryAllBoltRun`, `retryBoltRunFromFailure` — see [Bolt API](/developers/graphql-api/api-reference/bolt-api) |


## Related topics

- [Bolt](/developers/python-sdk/modules/bolt.md)
- [Run Details](/products/bolt/managing-schedules/run-details.md)
- [Schedule Settings](/products/bolt/creating-schedules/schedule-settings.md)
- [Build and Test Models with New Source Data](/products/bolt/creating-schedules/templates/dbt-tm-templates/deferred-model-execution.md)
- [bolt.run.completed](/developers/webhooks/bolt-run-completed.md)