Guide 09 · Developer docs

A job is a trigger, conditions and an ordered list of actions, set up under Customization › Orchestration in the admin; jobs were called hooks before the module was renamed, and the API's routes keep that name. What starts a job, what it can do, branches and loops, email, scheduled work, integrations with other systems, and every event and action.

L2–L3

Unit 06 of 08 3 pages

Scheduled jobs

Updated 23/10/2026 01:50

Jobs that run on the clock: how the scheduler queues them, how to process only what changed in chunks that finish in time, and how to find out when a scheduled job has stopped.

Start with how a schedule becomes a run: the scheduler and its tasks, the job queue, and the rule that every scheduled job must be safe to re-run from the start, because a run that fails halfway is not resumed. Then build the job itself: a watermark so each run takes only what changed, keeping it consistent across timezones so it does not reprocess the same records for ever, and a chunk size that keeps each run well inside its interval. Finish with monitoring, the page to read before a job goes live: how a scheduled job can stop, and the heartbeat or health check that tells you.

How a schedule is set on a job is in the unit on what starts a job (Web events and schedules); this unit assumes it.

In this unit

Read in order

01 Scheduler tasks and the job queue How work on the clock runs: the scheduler and its tasks, the difference between a platform task and a job with a schedule, how a scheduled run goes through the job queue, and what a run that fails halfway leaves behind. 02 Watermarks and chunking Process only what changed since the last run with a watermark, select the records in a template, keep the watermark consistent across timezones so it does not reprocess the same records on every run, and size chunks so each run finishes well inside its interval. 03 Finding out a scheduled job stopped A scheduled job that stops needs its own alert: nothing built in reports a stopped or missed run. The ways it can stop, and two patterns to catch it: an outbound heartbeat and an inbound health check.

Objects ReferenceGenerated from the platform, so it is always current

API ReferenceEvery REST endpoint, in cURL, PHP, Python and JavaScript

Scheduled jobs

In this unit