Clock
You can run a workflow automatically at a particular date or time.
Triggers
- Clock - Triggers at a specific date or time
Advanced (Cron)
When configuring the Clock trigger, you can set the Trigger Type to Advanced (Cron) to define a CRON expression for scheduling workflow runs in Coordinated Universal Time. The minimum supported interval is 1 minute.
A CRON expression consists of five fields, each representing a specific value:
| 1 | 2 | 3 | 4 | 5 |
|---|---|---|---|---|
| * | * | * | * | * |
| Minute (0–59) | Hour (0–23) | Day of the month (1–31) | Month (1–12) | Day of the week (0–6) |
Examples of supported CRON expressions:
| CRON Expression | Schedule |
|---|---|
| ***** | Every minute |
| 0**** | Every hour at minute 0 |
| 00*** | Every day at midnight |
| 00**FRI | At midnight, only on Friday |
| 001** | At midnight, on Day 1 of the month |
You can alternatively use online tools to generate valid CRON expressions as needed.
Note:
- If you set a clock trigger and enable the Disable Concurrent Execution field, the trigger waits for the current workflow instance to finish before starting a new one. This means that the workflow will only run once the previous instance completes, whether it succeeds, times out, or fails. For example, if a workflow takes 2 minutes to complete and the trigger runs every 5 minutes, normally a new instance starts every 5 minutes. With Disable Concurrent Execution set to true, the trigger waits 7 minutes to ensure that the current workflow is finished before starting a new one. This prevents concurrent execution of the same workflow.
- The Coordinated Universal Time time zone option is available in clock trigger version 9. Important: Select the Coordinated Universal Time time zone to prevent the confusion caused by Daylight Saving Time (DST) changes in your chosen regional time zone.
- You can set the clock trigger for a future date and time only.
- Seconds and years are not supported in CRON expressions.