Overview
Schedules
Section titled “Schedules”Run an agent or a flow on a schedule: a cron expression in a timezone. Each occurrence is one fire, which starts one run as the schedule’s owner (re-checked at every fire), through the same path as POST /v1/runs; a run a schedule started names it (Run.trigger). After a gap, catchUp runs once for the latest missed occurrence (or skips them), never once per missed one; overlap skips an occurrence while the previous run is still going. GET …/fires is the schedule’s history; run-now fires it outside the schedule. Mounted when the deployment fires schedules.