When "Run as Scheduled" is selected, command status will be enabled by default which indicates that the command will run as per schedule. You can use the following format to fill in the values of "* * * * *" to indicate how you plan to schedule the running command.
Sure, here are a few examples of how to specify CRON job schedules:
1. Run a job every minute:
```
* * * * * command to be executed
```
2. Run a job every hour at the 30th minute:
```
30 * * * * command to be executed
```
3. Run a job at 5 AM every day:
```
0 5 * * * command to be executed
```
4. Run a job at 5 AM every Monday:
```
0 5 * * 1 command to be executed
```
5. Run a job at 5 AM on the first of every month:
```
0 5 1 * * command to be executed
```
6. Run a job at 5 AM on June 1st:
```
0 5 1 6 * command to be executed
```
Note: In each of these examples, you would replace "command to be executed" with the actual command you want to run.
The CRON time string format is as follows:
```
* * * * * command to be executed
- - - - -
| | | | |
| | | | +----- day of the week (0 - 6) (Sunday=0)
| | | +------- month (1 - 12)
| | +--------- day of the month (1 - 31)
| +----------- hour (0 - 23)
+------------- min (0 - 59)
```
This is a very flexible system that allows for a high degree of customization of job scheduling.
Field | Format of valid values |
Minute | 0-59 |
Hour | 0-23 |
Day of the month | 1-31 |
Month | 1-12 (or JAN to DEC) |
Day of the week | 0-6 (or SUN to SAT; Sunday=0) |
By default, you are creating a command template so the scheduled command won't be activated. You can activate it by toggling "Command Status" or later on the Command page to activate the scheduled command.
