4. Trigger Types

After configuring the Command Settings of a Bolt Schedule, you’ll define trigger conditions to specify when the schedule should initiate runs. Bolt Schedules support four distinct trigger types, each designed for specific use cases and workflows.

​

Available Trigger Types

​

Detailed Trigger Type Configurations

​

Scheduled Run

Purpose: To automate jobs on a fixed schedule using cron syntax. How it Works: Specify the timing and frequency with cron expressions, such as hourly, daily, weekly, or custom intervals.

​

Configuration:

1. From the Bolt UI, select Scheduled Run as the Trigger Type
2. Add cron expression - you can use some of the preset option from the dropdown or build your own
3. (Optional) Select your timezone to ensure schedules execute at the correct time for your location and business hours
   • Default: UTC (schedules run in Coordinated Universal Time)
4. For Manual (Ad-hoc) runs, simply set the cron schedule to OFF.

---

​

On Run Completion

Purpose: Initiates a Bolt Schedule once another specified Bolt Schedule completes, ensuring dependency-based execution for sequential workflows. How it works: This trigger starts a Bolt Schedule only after a designated “parent” job finishes, creating a dependency chain.

​

Configuration

1. From the Bolt UI, select On Run Completion as the Trigger Type
2. In the Workspace Name dropdown, select the Paradime Workspace containing the triggering Bolt Schedule.
3. In the Bolt Schedule Name dropdown, select the specific Bolt Schedule that will act as the trigger.
4. Select in which event the “parent” Schedule will trigger this new run, you can choose between:
   1. Passed: the schedule will be trigger only if the “parent” complete successfully
   2. Failed: the schedule will be trigger only if the “parent” complete and contains errors
   3. Both Passed & Failed: the schedule will be trigger only irrespective of the “parent” status after completion

---

​

On Merge

Purpose: Automatically runs Bolt pipelines when code is merged into designated branches in your Git repository.

​

Configuration:

1. From the Bolt UI, select On Merge as the Trigger Type
2. Click Deploy to publish your schedule.

---

​

Bolt API

Purpose: Allows external systems or custom scripts to programmatically trigger jobs via REST API. How it Works: Uses Paradime’s REST API endpoints to initiate jobs based on events or actions outside of Paradime. Configuration: When configuring a Bolt schedule and wants to trigger this via the Paradime API, select the Scheduled run trigger type click on the OFF button to let the Schedule being trigger only via the API. For detailed configuration steps, refer to the Bolt API and Webhooks documentation.

---

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