Schedules
Schedule workflows to run automatically on a recurring interval from the CLI.
On this page5
The schedule family (alias schedules) configures automatic, recurring runs of a
workflow. A workflow can have at most one schedule.
Command summary
| Subcommand | Description |
|---|---|
schedule create [workflow-id] | Create a schedule for a workflow |
schedule rm <id> | Delete a schedule |
schedule ls | List schedules |
schedule get <id> | Get a schedule |
schedule enable <id> | Enable a schedule |
schedule disable <id> | Disable a schedule |
schedule create
Create a recurring schedule. The workflow can be given positionally or with
--workflow:
trickest schedule create 7b4a4059-… \
--date "2026-03-15T06:00:00Z" \
--repeat 86400 \
--parallelism 10| Flag | Description |
|---|---|
--workflow <name-or-id> | Workflow to schedule (fallback for the positional arg) |
--date <iso-8601> | First run time, e.g. "2026-03-15T06:00:00Z" |
--fleet <name-or-id> | Fleet to run on (defaults to managed) |
--repeat <seconds> | Repeat interval in seconds (e.g. 86400 = daily) |
--parallelism <N> | Machine count (1–1000) |
Common intervals for --repeat: 3600 (hourly), 86400 (daily), 604800 (weekly).
schedule rm
trickest schedule rm <schedule-id>
trickest schedule rm <schedule-id> --dry-run # preview what would be deletedReading a schedule
Use the workflow to inspect its schedule:
trickest workflow get 7b4a4059-… | jq '.schedule_info'schedule_info is null when the workflow has no schedule, or an object describing
the cadence when it does.