...
- single occurances
- repeating
One time events
| Code Block | ||
|---|---|---|
| ||
schedule <domain> event <eventtype> at <ISO8601 DateTime> [with <modifier_clause> | attributes <expr>] [setting(<var>)] |
...
The setting(<var>) clause stores the identifier for this scheduled event in the <var>. Note that <var> is a variable for the current rule and goes out of scope when the rule terminates, so it must be used inside the postlude where the scheduled event is created.
Recurring events
The format is the same as for single events; however the keyword repeat (instead of at) requires <timespec> to be a CRON style time specification (see below).
...
| Info | ||
|---|---|---|
| ||
The classic pico engine enforces a minimum period for scheduled events. The default is 599 seconds and can be configured. |
Complex expressions can be defined with a <timespec>. The extent of the CRON format is beyond the scope of this article, but some examples of recurring events that can be expressed through a cron <timespec> are
...