Skip to main content

Schedules

A schedule runs one or more jobs on cron expressions, in order or in parallel groups.

Schedules in the sidebar lists them with Name, Schedule (the first cron line, then "+N more"; hover for all of them and the time zone), Last run outcome, Last run completed, Next scheduled run, Enabled and actions: Run now / Stop run, lineage, View log and Copy API trigger URL (Standard and Enterprise). It is the landing page after sign-in.

The schedule form​

  • Name (unique), Description, Enabled.
  • Jobs — run in the order listed; the arrows reorder them. Tick With previous on a job to start it at the same time as the one above it; the job after such a group waits for all of them. The summary reads, for example, "Runs as 1 → 2+3 → 4". Continue running the remaining jobs if one fails decides whether a failed job stops the schedule; with it on, a schedule with a failed job ends completed with failures.
  • When to run — one or more cron lines, each built from a Recurrence (every N minutes or hours, daily at a time, weekly on chosen days, monthly on a day), optionally limited to certain hours or weekdays, or typed as a cron expression. A plain-English sentence confirms each line. No lines means manual runs only. Times use the install's Timezone from Setup → Runtime; the zone in force is saved on the schedule when it is saved.
  • Notifications — Failure email recipients get an email when the schedule ends in any non-success state, and Webhook subscriptions (Enterprise) POST its events. Job-level notifications fire independently.

Save re-locks the schedule form; the pencil reopens it.

Run a schedule​

Run now offers From the beginning or Start at a job, with the job's Phase and Activity pickers underneath: earlier jobs do not run, the chosen job starts where you say, and the jobs after it run in full.

A schedule never runs twice at once. A cron firing or a trigger that lands while a run is in progress is recorded as skipped with the reason, not queued. A disabled job inside a schedule is skipped and noted. Stop run stops all of the schedule's jobs.

The schedule's lineage view draws the jobs, parallel groups in a dashed box, and offers the same What runs next per job.