You can use the CRON format in the schedule builder to run your pipelines at specific dates and times if you find that the schedule builder interface does not meet your needs. You can use this to schedule pipeline runs, either as one-time events or as recurring tasks.
Each cron entry consists of five fields, specifying in the following order:
minute(s) hour(s) day(s) month(s) weekday(s)
| Field | Possible Values | Syntax | Example |
|---|---|---|---|
| minute(s) | 0 | 0 * * * * | By default, this value is 0. |
| hour(s) | 0 – 23 | 0 7 * * * | Runs any time the system clock shows 7am (7pm would be 19). |
| day(s) | 0 – 31 | 0 0 7 * * | Runs when the day of the month is 7 which means that the pipeline runs every 7th day of the month. L indicates the last day of the month. |
| month(s) | 0 = none and 12 = December | Runs when the numerical month is 7 which determines that the pipeline runs only in July. | |
weekday(s) | 0 = Sunday and 7 = Sunday | 0 0 0 7 * | 7 in the current position means that the pipeline would only run on Sundays. |
Restrictions
The following syntax is not supported:
- A seconds specifier
- Non-standard cron expressions, such as @yearly, @hourly, @weekly, and @reboot
Other restrictions include
- You can’t schedule a pipeline to run more than once per hour.
- The cron string must be split into 5 sections (minute, hour, day of month, month, day of week)
Not all cron syntax that you create in the advanced tab can be displayed in the basic tab.
Cron resources
For more information about using cron, see: