Schedule Settings¶
A recipe can contain several configured schedules, each associated with one or more variations. The following table outlines the scheduling settings
used in the UI forms and in the variations.json file.
Schedule settings and details¶
| Setting, field, and/or value | Details |
|---|---|
| Schedule Name | A unique name for this schedule. This field is not editable for existing schedules. |
| Frequency | The frequency section in the UI includes a series of choices: Every x minutes Every x hours Every x days On certain days of the week Every x months Advanced Your selection and configuration sets a Cron Expression and shows the Next Run. To specify your own frequency, select the Advanced option, then enter the Cron Expression as described below. |
Cron Expression or schedule value |
The statement of day/time for recurring order runs. An ISO 8601 scheduling expression. See Cron Expression Basics for details and information on setting advanced schedules. |
Time Zone or scheduleTimeZone value |
The time zone to associate with the schedule time, selected from the supported time zones list. The default value is UTC. See Cron Expression Basics for limitations regarding time zone designation. |
Max RAM or max-ram value |
The maximum memory resource allocation for the order run. If the order run passes this setting, it is automatically stopped. The value is expressed in MB. The default value is 1024 MB. For more information, see Schedules with Heavy Processing |
Max Disk Space or max-disk value |
The maximum disk space allocation for the order run. If passes this value the order run is automatically killed. The value is expressed in MB. The default value is 2048 MB. For more information, see Schedules with Heavy Processing |
Max Threads or max-threads value |
The maximum amount of threads. This can reduce the memory required by a recipe by having less nodes processed in parallel. The value is expressed as a positive integer. By default the order run will use as many threads as there are parallel nodes in the graph. For more information, see Schedules with Heavy Processing |
Annotations for Runtime Components or annotations value |
Metadata that can be included for use by external tools. See Annotations for more information. |