Skip to main content

Schedule lifecycle

Every scheduled job moves through a small set of states.

StateMeaningHow to leave it
DRAFTCreated but not active. Won't fire.Activate to make it live
PENDINGActive and waiting for the next fire timeAuto-transitions to RUNNING when due, or Pause to halt
RUNNINGA worker is executing right nowWait — or Cancel the active execution from the executions page
PAUSEDManually paused; no new runs fireResume to put it back in PENDING
DISABLEDAuto-disabled (consecutive failures) or manually disabledActivate again after fixing the underlying issue
COMPLETEDA ONE_TIME schedule already ranTerminal — clone if you need it again
FAILEDLast run failed and retries exhaustedResume after fixing, or check DLQ
ARCHIVEDSoft-deleted; won't fire, hidden by defaultRestore by editing the soft-delete field directly (workspace admin only)

Edit a schedule​

From the schedule detail page (/scheduler/:jobId) the Edit button opens an in-place editor. Saving creates a new version automatically — every change is tracked.

Versions​

The detail page has a Versions tab listing every revision with: who changed it, what fields changed, when, and the optional change reason. Click any version to view the full configuration snapshot.

Restore from a version rolls the live schedule back to that snapshot and creates a new version recording the restore.

Bulk operations​

From the list view, multi-select rows and apply:

  • Bulk pause
  • Bulk resume
  • Bulk archive
  • Bulk update (apply the same field changes to many schedules at once)

Bulk operations are atomic per row — if one fails, the others still apply, and the failure list shows which ones errored.

Clone​

The Clone action copies a schedule into a new draft so you can tweak it without affecting the original. The new schedule starts in DRAFT.

Run now​

The Run now action triggers an immediate execution outside the schedule. The recorded execution is tagged so you can tell it apart from regular runs in the executions list.