triggers: block, or create one directly with reliant trigger create.
Declaring a schedule
skip records a skipped firing in the history instead of starting a second run on top of the first. allow starts a concurrent run, which can pile up if each run takes longer than the gap between fires. The short catch-up window is deliberate: after an outage you get at most the last few minutes’ runs, not a replay of everything you missed.
From the CLI
--daemon (a machine id or hostname) and --message are required. --project defaults to the working directory. --preset, --param, --timezone, --overlap, --catchup-window and --disabled are optional.
Manage them afterwards with:
fire skips the enabled and overlap checks. Deleting a trigger keeps its firing history; the runs it started still exist.
Related topics
- Automations overview
- No-machine runs
- Cloud machines & plans, for what happens when the machine is asleep at fire time