Schedule
Starts a run on a timetable: every few minutes, every hour, every day at a time, on chosen days, or on any cron expression. Times are in UTC.
Kind
trigger:scheduleGroupStarts the workflow
CreditsFree
Ports out1
How it looks
Settings
| Setting | Required | What it does |
|---|---|---|
| Repeatcron | Yes | Pick every N minutes, hourly, daily, weekly or monthly and the console writes the cron expression for you, or type your own, like 0 6 * * * for 06:00 UTC each day. Next runs shows when it will fire. |
| Correlation keycorrelationKey | No | Which runs count as the same for the setting above. Left empty, each occurrence is its own. Set it to share one line with another trigger. |
Ports
| Port | The run leaves by it when |
|---|---|
default | At each scheduled time. |
What it adds to the run
Later nodes can read these, in a condition or as {{name}} in a text field.
| Value | Holds |
|---|---|
triggeredAt | When the trigger fired. |
Example
Water the plants at dawn
- Repeat daily at 05:30 UTC.
- Connect Send to client with command
pump.runand payload{ "seconds": 20 }.
If WBSKT was downOccurrences missed while the engine was restarting are fired one after another when it's back, so nothing is skipped.
Problems you might see
| Code | Means |
|---|---|
INVALID_CRON | The cron expression can't be read. The console checks it as you type. |
Problems found when you publish stop the publish and point at the node. Problems while a run is going fail the node, and its On failure setting decides what happens next. See the error codes for the API's own.
See also
Sends a command to a client. Can wait for the client to confirm and leave by what happened.
Outdefaultor, when waitingackedfailedtimeoutaction:clientMessagePauses the run for a fixed time. Waiting costs nothing.
Outdefaultcontrol:delaySets, increments or compare-and-sets a variable, local to the run or shared by every run.
Outdefaultcontrol:variable