# 1. Schedule Settings

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.

<figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2Fyiz8PV9Uk7I6BOYHAp1D%2Fimage.png?alt=media&#x26;token=12395ad9-b498-4b6c-a427-fda13ef024a8" alt=""><figcaption></figcaption></figure>

### Schedule Types

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

<table><thead><tr><th width="174">Schedule Type</th><th width="262">Description</th><th>When to Use</th></tr></thead><tbody><tr><td><a href="#standard-schedules"><strong>Standard</strong></a></td><td>Regular scheduled runs that execute your pipelines on a set schedule.</td><td><ul><li>Simple, time-based execution</li><li>Consistent, periodic runs</li><li>Basic scheduling needs</li></ul></td></tr><tr><td><a href="#deferred-schedules"><strong>Deferred</strong></a></td><td>Optimized runs that leverage manifest comparison between runs to optimize execution time and compute resources.</td><td><ul><li>Run only modified models that have changed between runs</li><li>Run only models with "fresher" data.</li><li>Re-run models from point of failure in previous runs</li><li>Deploy changes to models after a Pull Request in Merged as part of Continuous Deployment workflows (CD)</li></ul></td></tr><tr><td><a href="#turbo-ci-schedules"><strong>Turbo</strong> CI</a></td><td>Automated pull request validation that builds modified models and their dependencies in a temporary schema.</td><td><ul><li>CI workflows to test code changes</li><li>Automatic validation for pull requests</li></ul></td></tr></tbody></table>

### 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/embed flowId="zKFUvGit3zdr2PcNsYoZ" url="<https://app.arcade.software/share/zKFUvGit3zdr2PcNsYoZ>" %}

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

{% hint style="info" %}
**Tip**: Use **Last run** unless retrying builds
{% endhint %}

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

{% @arcade/embed flowId="33KUsoX1Wto6Ik0rrIjv" url="<https://app.arcade.software/share/33KUsoX1Wto6Ik0rrIjv>" %}

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

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Tip</strong>: Use <strong>Last run</strong> unless retrying builds</p></div>
8. **`Branch Selection:`** For Turbo CI, Bolt will execute the schedule when a PR is opened against your Main/Master branch.

{% @arcade/embed flowId="UL7BGGBDbhFShGU9w39e" url="<https://app.arcade.software/share/UL7BGGBDbhFShGU9w39e>" %}

***

Now, let's learn how to configure the [Command Settings](https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/command-settings) of a Bolt Schedule.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/schedule-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.