What it is
The Scheduling & Recurrence engine is the shared substrate behind anything in the platform that runs on a repeating schedule - delivering a report, re-running an access-review cycle, sweeping for due dates. Rather than every feature inventing its own timer, they register a scheduled job against this engine, and a single sweep fires them when they are due.
It provides three things:
- DST-safe recurrence math - it computes the next fire time for hourly, daily, weekly, monthly, quarterly, and yearly cadences, holding the intended wall-clock time across daylight-saving transitions in the job's timezone.
- A generic scheduled-jobs store - each job records its type, a human-readable recurrence, an enabled flag, the next and last fire times, a fire count, and the last result.
- A handler registry - a feature registers a handler for its job type; the sweep invokes that handler with the job's payload when the job is due.
How jobs run
A sweep runs every 15 minutes. It finds every enabled job whose next fire time has passed, invokes the registered handler for that job's type, records the result (ok / error / skipped), and advances the job to its next fire time. A job can be triggered immediately with run-now, which simply queues it to fire on the next sweep (within ~15 minutes). A job can be disabled to pause it without deleting it, and re-enabled later.
The recurrence is described in plain language wherever a job is shown - "Daily at 06:00 UTC", "Weekly on Mon", "Quarterly on day 1" - so the cadence is readable at a glance rather than as a cron string.
Where you see it
The engine is mostly infrastructural - it backs scheduled work that other features own (for example scheduled report delivery and recurring review cycles). Administrators and auditors can review the configured jobs, their cadence, and when each will next fire, to confirm that recurring work is set up and healthy.
MCP tool reference
| Tool | Purpose |
|---|---|
list_scheduled_jobs | List the organization's recurring scheduled jobs - job type, human-readable recurrence, enabled state, and next fire time. Optional job-type filter. Auditor+. |
Related
- Reports guide - scheduled report delivery is one consumer of the recurrence engine
- GRC guide - recurring access-review cycles and due-date sweeps
- MCP setup - connecting Claude Desktop / API to TATER