Cron expression reference
This solution uses a subset of the standard 5-field Linux cron format for recurring test schedules. The cron expression consists of five fields separated by spaces.
┌───────── minute (0-59) │ ┌─────── hour (0-23, *, */N, or comma list) │ │ ┌───── day of month (1-31 or *) │ │ │ ┌─── month (1-12 or *) │ │ │ │ ┌─ day of week (0-6, *, range, or list) │ │ │ │ │ 0 9 * * 1-5
Accepted values
The following table describes what each field accepts.
| Field | Accepted values | Examples |
|---|---|---|
|
Minute |
A single value from 0 to 59. |
|
|
Hour |
|
|
|
Day of month |
|
|
|
Month |
|
|
|
Day of week |
|
|
Day of week values use the following mapping: 0 = Sunday, 1 = Monday, 2 = Tuesday, 3 = Wednesday, 4 = Thursday, 5 = Friday, 6 = Saturday.
Unsupported patterns
The following patterns are valid Linux cron syntax but are not supported by this solution.
| Pattern | Example | Reason |
|---|---|---|
|
Minute step values |
|
The minimum scheduling interval is one hour. |
|
Minute lists |
|
The minimum scheduling interval is one hour. |
|
Day of month ranges |
|
Only a single day value or wildcard is accepted. |
|
Day of month lists |
|
Only a single day value or wildcard is accepted. |
|
Month ranges |
|
Only a single month value or wildcard is accepted. |
|
Month lists |
|
Only a single month value or wildcard is accepted. |
|
Question mark |
|
The question mark character is not valid in standard Linux cron. Use |
Preset patterns
The web console provides the following preset patterns that you can select with a single click.
| Pattern name | Expression | Description |
|---|---|---|
|
Every hour |
|
Runs at minute 0 of every hour. |
|
Daily at 9:00 AM |
|
Runs once daily at 9:00 AM in the selected timezone. |
|
Weekdays at 8:00 AM |
|
Runs Monday through Friday at 8:00 AM. |
|
Every Sunday at 5 PM |
|
Runs every Sunday at 5:00 PM. |
|
1st of month at 11 AM |
|
Runs on the first day of every month at 11:00 AM. |
Scheduling constraints
-
The minimum interval between scheduled test runs is one hour. The system validates that the interval between consecutive runs is longer than the estimated test duration.
-
An expiry date is required for all recurring schedules. Tests will not run after the end of the expiry date (UTC).
-
The schedule timezone determines when the cron fires. Daylight Saving Time transitions are handled automatically. If a scheduled time does not exist due to a DST spring-forward transition, that occurrence is skipped.
-
The system validates the cron expression on both the web console and the API. If the expression does not match the accepted format, the test cannot be created.