Schedule a job

A schedule uses a cron expression, and it can fire a stored template, a single run, a split, or a whole pipeline.

Schedule a template

1. Save the work first as a template, so the schedule stays a one-line reference instead of a copy of every field.
2. Open Schedules and add a schedule.
3. Give it a cron expression for the cadence, for example 0 2 * * * for 02:00 every day, and point it at the template.
4. Save. It fires on the schedule and each firing shows up in Runs like any other.

From the API

curl -s -X POST localhost:8080/v1/schedules \
  -H 'content-type: application/json' \
  -d '{"cron":"0 2 * * *","template_id":"tpl_abc123"}'

To schedule without a template, send playbook and inventory inline, add shards for a split, or steps for a pipeline. A worker or the server must be running for a schedule to fire. Add capacity with switchtender worker.

By default the cron expression reads in the server's local time. Add a timezone, an IANA name such as America/New_York, to pin it to a zone and let it follow that zone's daylight-saving shifts, so a nightly window stays put across the year.

curl -s -X POST localhost:8080/v1/schedules \
  -H 'content-type: application/json' \
  -d '{"cron":"0 2 * * *","timezone":"America/New_York","template_id":"tpl_abc123"}'

Next: give the job its secrets with set a secret.