Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

SOP Fan-In: Cron

Wired. Cron triggers are dispatched by the periodic SOP maintenance tick, so this is a poller rather than a per-schedule timer. Firing needs that tick, which a zeroclaw daemon or the zeroclaw channel start supervisor spawns (built with the agent-runtime feature, sop.sops_dir set, and sop.maintenance_interval_secs non-zero, default 60). Standalone zeroclaw gateway start does not spawn the maintenance tick, so it does not fire cron triggers; a gateway hosted inside the daemon does, because the daemon spawns the tick. Schedules are parsed once at startup, so a SOP added while the daemon is running needs a reload before its cron trigger takes effect.

A cron trigger fires on a time window described by a cron expression. Invalid expressions fail closed during parsing and cache build.

Trigger

Time-based firing. Live: dispatched by the SOP maintenance tick (daemon / channel-start paths).

fieldtypedefaultmeaning
expression*string—Cron expression evaluated over the run window.

Load and verify the SOP:

Define

Author the SOP as described in Syntax, with a cron trigger. The trigger fields above are the supported keys; the page walks the full file.

Validate

zeroclaw sop validate

Inspect

zeroclaw sop list
zeroclaw sop show <name>

See also