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

# 1. Schedule Settings

> Configure Bolt schedule parameters including type selection, branch settings, and basic configuration options for Bolt schedules.

export const Arcade = ({src, title}) => <div style={{
  position: 'relative',
  paddingBottom: 'calc(56.2225% + 41px)',
  height: 0,
  width: '100%'
}}>
    <iframe src={src} title={title} frameBorder="0" loading="lazy" allow="clipboard-write" allowFullScreen style={{
  position: 'absolute',
  top: 0,
  left: 0,
  width: '100%',
  height: '100%',
  colorScheme: 'light'
}} />
  </div>;

The first step when creating a Bolt Schedule is to configure the Schedule Settings. Select the schedule type, provide a descriptive name, choose the branch to trigger runs, and add an optional description for easy reference.

<Frame>
  <img src="https://mintcdn.com/paradime-docs/KJcB9NhKTmxLMoZP/images/image-110.png?fit=max&auto=format&n=KJcB9NhKTmxLMoZP&q=85&s=944a1faafc15b9775ee06b18cebb6e68" alt="" width="626" height="492" data-path="images/image-110.png" />
</Frame>

### Schedule Types

Bolt Schedules offer three separate schedule types in the schedule settings:

| Schedule Type                                                                          | Description                                                                                                     | When to Use                                                                                                                                                                                                                                                    |
| -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**Standard**](/products/bolt/creating-schedules/schedule-settings#standard-schedules) | Regular scheduled runs that execute your pipelines on a set schedule.                                           | • Simple, time-based execution• Consistent, periodic runs• Basic scheduling needs                                                                                                                                                                              |
| [**Deferred**](/products/bolt/creating-schedules/schedule-settings#deferred-schedules) | Optimized runs that leverage manifest comparison between runs to optimize execution time and compute resources. | • Run only modified models that have changed between runs• Run only models with "fresher" data.• Re-run models from point of failure in previous runs• Deploy changes to models after a Pull Request in Merged as part of Continuous Deployment workflows (CD) |
| [**Turbo** CI](/products/bolt/creating-schedules/schedule-settings#turbo-ci-schedules) | Automated pull request validation that builds modified models and their dependencies in a temporary schema.     | • CI workflows to test code changes• Automatic validation for pull requests                                                                                                                                                                                    |

### Creating Schedules

#### Standard Schedules

Regular scheduled runs that execute your pipelines on a set schedule.

1. Go to **Bolt**, click **`Create New Schedule`**
2. **Schedule Type**: Select **`Standard`**
3. **Name**: Use a clear, descriptive name (e.g., "daily-backup-prod", "weekly-data-cleanup")
4. **Description**: (Optional) Add a brief purpose statement
5. **Owner Email**: Assign an owner
6. **Branch Selection**: Select the Git branch for execution (main/master or a feature/staging branch)

<Arcade src="https://demo.arcade.software/zKFUvGit3zdr2PcNsYoZ?embed&embed_mobile=tab&embed_desktop=inline&show_copy_link=true" title="1. Schedule Settings" />

#### Deferred Schedules

Optimized runs that leverage manifest comparison between runs to optimize execution time and compute resources.

1. Go to **Bolt,** click **Create New Schedule**
2. **Type**: Select **`Deferred`**
3. **Name**: Use a clear, descriptive name
4. **Description**: (Optional) Add a brief purpose statement.
5. **Owner Emai**: Assign an owner
6. **Deferred Schedule**: Choose which schedule name Bolt should be using for deferral, this is about defining in which schedule Paradime should look for the `manifest.json`, `run_results.json`, or `sources.json`
7. For **Last Run Type**, choose between the following:
   1. **`Last run`**: Retrieves artifacts from the most recent run.
   2. **`Last successful run`**: Uses artifacts from the last successful run, skipping incomplete run

<Info>
  **Tip**: Use **Last run** unless retrying builds
</Info>

17. **Branch Selection**: Select the Git branch (main/master or a feature/staging branch).

<Arcade src="https://demo.arcade.software/33KUsoX1Wto6Ik0rrIjv?embed&embed_mobile=tab&embed_desktop=inline&show_copy_link=true" title="1. Schedule Settings" />

#### Turbo CI Schedules

Automated pull request validation that builds modified models and their dependencies in a temporary schema.

1. Go to **Bolt**, click **`Create New Schedule`**
2. **Schedule Type**: Select **`Turbo CI`**
3. **Name**: Use a clear, descriptive name
4. **Description**: (Optional) Add a brief purpose statement
5. **Owner Email**: Assign an owner
6. **`Deferred Schedule:`** Choose which schedule name Bolt should be using for deferral, this is about defining in which schedule Paradime should look for the `manifest.json`, `run_results.json`, or `sources.json`
7. For **Last Run Type**, choose between the following:

   1. **`Last run`**: Retrieves artifacts from the most recent run.
   2. **`Last successful run`**: Uses artifacts from the last successful run, skipping incomplete run

   <p><strong>Tip</strong>: Use <strong>Last run</strong> unless retrying builds</p>
8. **`Branch Selection:`** For Turbo CI, Bolt will execute the schedule when a PR is opened against your Main/Master branch.

<Arcade src="https://demo.arcade.software/UL7BGGBDbhFShGU9w39e?embed&embed_mobile=tab&embed_desktop=inline&show_copy_link=true" title="1. Schedule Settings" />

***

Now, let's learn how to configure the [Command Settings](/products/bolt/creating-schedules/command-settings/index) of a Bolt Schedule.&#x20;


## 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)
- [Paradime Turbo CI Schema Cleanup](/products/bolt/ci-cd/turbo-ci/paradime-turbo-ci-schema-cleanup.md)