> ## 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.

# Schedule Settings

> Name a Bolt schedule, set its owner and Git branch, and optionally defer to a previous run to compare state and build incrementally.

Schedule settings define the schedule's identity and the Git branch it runs against, plus optional deferral so a run can compare its state against a previous run.

## Settings

| Field           | Required | Description                                                                                                                                                                                                                          |
| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Name**        | Yes      | A clear, descriptive name for the schedule (for example, `daily-prod-build`).                                                                                                                                                        |
| **Description** | No       | A short note on the schedule's purpose, for easy reference.                                                                                                                                                                          |
| **Owner email** | Yes      | The email of the schedule owner.                                                                                                                                                                                                     |
| **Git branch**  | Yes      | The branch used to trigger runs (for example, `main`, or a feature or staging branch). Click **Refresh** to reload the branch list after pushing a new branch.                                                                       |
| **Environment** | No       | The Bolt [environment](/products/settings/connections/index#create-and-manage-environments) the schedule runs in. The environment determines the warehouse connection the run uses. Defaults to the workspace's default environment. |

## Defer to a previous run

Turn on **Defer to a previous run** to compare state against a previous run instead of building the whole project. This is how you run incrementally: build only the models that changed, refresh only models with newer source data, or re-run from the point of failure. It also powers Continuous Deployment, where a merge deploys only what changed.

When the toggle is on, configure:

* **Deferred schedule** — the schedule Bolt reads run artifacts from (`manifest.json`, `run_results.json`, and `sources.json`) to work out what changed.
* **Last run type (for comparison)** — which run of the deferred schedule to compare against:
  * **Last run** — the most recent run.
  * **Last successful run** — the last run that passed, skipping incomplete or failed runs.

<Info>
  **Tip:** Use **Last run** unless you are retrying builds, in which case **Last successful run** avoids comparing against a broken state.
</Info>

<Tip>
  Turbo CI schedules always defer, since they build only the models changed in a pull request. See [Triggers](/products/bolt/creating-schedules/trigger-types#turbo-ci) and [Turbo CI](/products/bolt/ci-cd/turbo-ci/index).
</Tip>

***

Next, set up [Self-healing](/products/bolt/creating-schedules/self-healing) to automatically recover from failed runs.

<Card title="Define this as code" icon="code" href="/products/bolt/creating-schedules/schedules-as-code/configuration-reference#base-configuration" horizontal>
  Set `name`, `description`, `owner_email`, and `git_branch` in the base config, and `deferred_schedule` for [deferral](/products/bolt/creating-schedules/schedules-as-code/configuration-reference#deferred-artifacts).
</Card>


## Related topics

- [Test Code Changes On Pull Requests](/products/bolt/creating-schedules/templates/ci-cd-templates/test-code-changes-on-pull-requests.md)
- [Re-executes the last dbt™ command from the point of failure](/products/bolt/creating-schedules/templates/dbt-tm-templates/re-executes-the-last-dbt-command.md)
- [Snapshot Source Data Freshness](/products/bolt/creating-schedules/templates/dbt-tm-templates/snapshot-source-data-freshness.md)
- [Run and Test all your dbt™ Models](/products/bolt/creating-schedules/templates/dbt-tm-templates/run-and-test-all-your-dbt-tm-models.md)
- [Turbo CI Schema Cleanup macro for dbt™](/products/bolt/ci-cd/turbo-ci/paradime-turbo-ci-schema-cleanup.md)