Schedules and schedule policies
A schedule is a Schedule Trigger node on a workflow, for canvas workflows and durable functions alike, so it is versioned with the workflow and fires for the active version. Schedule policies decide what a fire does when the previous run is still open, how missed fires are caught up, and when the schedule stops. This page covers the policies and the schedule controls; the trigger's rules (every hour, every weekday at 9:00, a cron expression) are described in Schedule Trigger.
Setting a policy
Open the Schedule Trigger node and its Schedule tab, then Use a policy. Policy changes apply when the workflow is saved and activated.
| Setting | Meaning |
|---|---|
| When the previous run is still open | The overlap policy (below). Without a policy every fire starts a run, as schedules always did |
| Catch-up window (seconds) | After the scheduler was unavailable, missed fire times inside this window are run, each as its own catch-up run with its own planned time, oldest first. Older ones are skipped and recorded. At most 7 days |
| Stop after this many runs | The schedule completes after this many fires |
| Pause the schedule when a run it started fails | A failed run pauses the schedule until someone unpauses it |
| Overlap policy | When a fire finds the previous run still open |
|---|---|
Skip the fire (SKIP) | The fire is skipped and recorded. The default when you choose a policy |
Run once after it ends (BUFFER_ONE) | One fire is held and starts when the open run ends; later ones are skipped |
Run every missed fire after it ends (BUFFER_ALL) | Every fire is held (up to 1,000) and they start one after another |
Cancel it and start (CANCEL_OTHER) | The open run is asked to cancel, then the new run starts |
Terminate it and start (TERMINATE_OTHER) | The open run is terminated, then the new run starts |
Start anyway (ALLOW_ALL) | Runs overlap |
Fire times beyond the trigger's rules
When the schedule fires chooses between the trigger's own rules (its Parameters tab) and fire times defined in the panel:
- Cron expression, with 5 or 6 fields.
- Calendar entries: each field takes values, ranges and steps (
1,15,1-5,0-59/15). Every field of an entry must match. Empty second, minute and hour mean 0; empty date fields mean any day. Day of week 0 is Sunday. - Intervals: fire at every multiple of a length since 1970-01-01 UTC, moved by an optional offset.
With fire times defined here you can also set:
- Start and End: the schedule fires only between them.
- Time zone: empty uses the trigger's time zone. Intervals always run on UTC.
- Jitter: each fire waits a random time up to this long, at most 7 days, so many schedules do not fire at the same instant.
- Excluded calendars: a fire time that matches any of them is skipped and recorded as excluded, for example public holidays.
Choosing the trigger's rules again drops these fire times with their window, jitter and excluded calendars.
What every run receives
- Schedule context: a JSON object the run reads as
context.scheduleContext. - Search attributes: a JSON object of search attributes stamped on every run the schedule starts. A name the workspace has not defined is left out when the run starts.
Controlling a schedule
Once the workflow is saved, the Schedule tab shows whether the schedule is Active or Paused, its Next fire times and its Recent actions: each planned time and what became of it (FIRED, SKIPPED_OVERLAP, BUFFERED, DELAYED, DROPPED_CATCHUP, EXCLUDED, SKIPPED_PAUSED and so on). From there:
- Trigger now starts one run now. It counts as one run.
- Pause, with an optional note, and Unpause.
- Backfill runs the fire times between From and To, at most 1,000 past fire times. Each started run counts toward your monthly runs.
The same from the CLI:
fluidgrids schedules list
fluidgrids schedules describe nightly-restock tick # spec, state, next fire times, recent actions
fluidgrids schedules trigger nightly-restock tick
fluidgrids schedules backfill nightly-restock tick --from 2026-10-01T00:00:00Z --to 2026-10-02T00:00:00Z
fluidgrids schedules pause nightly-restock tick --note 'stocktake in progress'
fluidgrids schedules unpause nightly-restock tick
The two arguments are the workflow key and the Schedule Trigger node's id. The Schedules page in the sidebar lists every schedule of the workspace; see Schedules.
In code
A durable function declares its schedule as its trigger (trigger: { operation: triggers.schedule, args }). The declaration is a default for the first push; after that the trigger, policy included, is owned by the workflow definition, so set or change the policy in the Schedule tab and fluidgrids pull brings it into the code.