Timetable Setting
This section should describe how to specify WHEN schedule should be triggered. Please keep in mind, that exact trigger times are not guaranteed. There may be couple of seconds delay. Schedule itself can be specified in different ways.
Onetime Schedule
It is obvious, that this schedule is triggered just once.
Table 5.1. Onetime schedule attributes
| Type | "onetime" |
| Start date/time | Date and time, specified with minutes precision. |
Periodical schedule by Interval
This type of schedule is the simplest periodical type. Trigger times are specified by these attributes:
Table 5.2. Periodical schedule attributes
| Type | "periodic" |
| Periodicity | "interval" |
| Start date/time | Date and time, specified with minutes precision. |
| End date/time | Date and time, specified with minutes precision. |
| Interval in minutes | Specifies interval between two trigger times. Next task is triggered even if previous task is still running. |
| Fire misfired ASAP switch | If checked and trigger time is missed because of any reason (i.e. server restart), it will be triggered immediately, when it is possible. Otherwise it is ignored and it will be triggered at next scheduled time. |
Periodical schedule by timetable (Cron Expression)
Timetable is specified by powerful (but a little bit tricky) cron expression.
Table 5.3. Cron periodical schedule attributes
| Type | "periodic" |
| Periodicity | "interval" |
| Start date/time | Date and time, specified with minutes precision. |
| End date/time | Date and time, specified with minutes precision. |
| Cron expression | Cron is powerful tool, which uses its own format for scheduling. This format is well known among UNIX administrators. i.e. "0 0/2 4-23 * * ?" means "every 2 minutes between 4:00am and 11:59pm". |
| Fire misfired ASAP switch | If checked and trigger time is missed because of any reason (i.e. server restart), it will be triggered immediately when it is possible. Otherwise it is ignored and it will be triggered at next scheduled time. |
