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.

​

Schedule Types

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

​

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)

​

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

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

​

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

   Tip: Use Last run unless retrying builds

8. Branch Selection: For Turbo CI, Bolt will execute the schedule when a PR is opened against your Main/Master branch.

---

Now, let’s learn how to configure the Command Settings of a Bolt Schedule.