Schedules¶
Set schedules to run orders on a routine basis, assign runtime resources, or add order annotations.
Overview¶
A recipe must contain at least one schedule that indicates when an order should be processed, its repetition properties, and its retry interval. Recipe variations can share schedules, schedules can be configured but remain unused (i.e. not assigned to a variation), and schedules can be created without a frequency.
Schedules are configured in the UI or CLI and details are recorded in the recipe's variations.json file.
Note that if an order run misses its scheduled start time for any reason, the system will continue to attempt to execute the order for up to 120 seconds.
On demand order runs¶
Recipe variations with—or without—schedules can be run at any time.
For details on how to, see Run an Order.
Schedule syntax¶
The Kubernetes-based Automation agents expect order schedules to follow cron syntax.
See Cron Expression Basics for more information.
Time zone support¶
Order scheduling provides time zone support. See Supported Time Zones for a complete list of the time zones the system accepts.
If no time zone is applied, Coordinated Universal Time (UTC) is used by default.
Manual schedule controls¶
Schedules are active once an order schedule is set up and the first order has been run.
You can stop orders with active schedules, either temporarily or permanently, using the controls on the Orders page.
- Stop: halts an active schedule permanently.
- Pause: places an active schedule on a temporary pause, until it is resumed. Order runs in progress continue to execute, but no new order runs are generated.
- Play: resumes a paused schedule. Scheduled order runs missed during the paused time are not run.