Available in VPC.
A Run can be executed as a one-off run or as a recurring run. A recurring run is a repeated execution, and it supports Periodic and Cron formats as run triggers. When configuring Cron-based triggers, use the following Cron format:
| Field name | Mandatory | Allowed values | Allowed special characters |
|---|---|---|---|
| Seconds | Yes | 0-59 | * / , - |
| Minutes | Yes | 0-59 | * / , - |
| Hours | Yes | 0-23 | * / , - |
| Day of month | Yes | 1-31 | * / , - ? |
| Month | Yes | 1-12 or JAN-DEC | * / , - |
| Day of week | Yes | 0-6 or SUN-SAT | * / , - ? |
You can enable or disable recurring execution from the Recurring Runs interface, and you can also limit the maximum number of concurrent runs.
| Component | Description |
|---|---|
| Trigger type | If you select Periodic, the Run executes at the specified time interval. If you select Cron, the Run executes according to the provided Cron expression. |
| Maximum concurrent runs | Specifies the maximum number of Runs that can run simultaneously. When multiple Runs are triggered at once, this setting limits the number that can run at the same time. For example, this setting is useful when Catchup is enabled. |
| Has start date | Specifies the earliest time the Run can start. Both future and past timestamps are allowed. If you set a past start date and enable Catchup, all Runs that should have executed since that time will be triggered. |
| Has end date | Specifies the latest time the Run can be executed. Both future and past timestamps are allowed. After this time, no additional Runs will be triggered. |
| Catchup | When enabled, all missed Runs that should have executed are run. All runs that should have been executed from the start date set in the past up to the end date or up to the current time will be executed. |
| Run every | Defines the execution interval for Periodic scheduling. |
| Cron expression | (Displayed when Trigger type is set to Cron) Enter a Cron expression directly to define the schedule. |