Schedules

A schedule runs a workflow on a clock instead of on a visit: hourly, nightly, Mondays at 9am. It's how data stays fresh with nobody touching it: pull a feed each morning, rebuild a summary, send a weekly digest.

#Two ways to recur

• Every N minutes or hours, the simplest: "every 15 minutes," "every 2 hours." Good for keeping something continuously current.
• On a cron schedule: a calendar-aligned time in a timezone you choose, e.g. 09:00 every Monday. The timezone is honoured with daylight-saving in mind, and the editor previews the next few run times as you set it. Daily and longer cadences belong here.

A schedule can also pass a fixed input to its workflow on every run.

#Running it

You switch a schedule on or off, and can run it now to test without waiting for the next fire. Each run is recorded. See Runs and monitoring to read history and failures. A scheduled run spends credits like any other; see Credits and caching.

#Long jobs

A schedule is where a chain belongs: a workflow that finishes one run, saves a bookmark, and starts another run to carry on. Every link after the first runs in the background, so nothing is waiting on it. In the run history, one fire of such a schedule shows as several links, in order, each with its own outcome and trace.