Skip to main content
Three subcommands manage an installation’s recurring schedule. They take an installation id, from jstm agent installations — not an agent id.

schedule show

Show the schedule, when it last fired, and the server-computed next fire time.
Last fired shows until the schedule fires once. Next fire is computed by the server as the first scheduled time strictly after now, so a frequent schedule never shows a time that has passed.
Emit as JSON.

schedule set

Set the cron schedule. The expression is validated locally before any request, so a typo fails immediately with nothing changed.
required
A standard five-field cron expression, evaluated in UTC.
default:"dry_run"
Run mode: dry_run or live.
Emit as JSON.
set sends the run mode on every call and defaults it to dry_run. Running set again with only --cron silently reverts a live schedule to dry_run. Always repeat --env live when changing a live schedule.

schedule clear

Remove the schedule. The agent stays installed and can still be run manually or by other triggers.

Cron expressions

All expressions are evaluated in UTC. There is no per-schedule timezone.

Behavior worth knowing

If the scheduler is down across several scheduled times, it fires the most recent missed one once on recovery, not a burst for every time it missed. Changing a schedule resets its clock to the next future time. It will not back-fire for a time that has already passed.

See also