Maintenance & Conformance
Two kinds of thing run in the background on a schedule. Sweeps keep the system tidy — clearing out what has expired, finishing what was left half-done. Conformance runners prove a subsystem still works and raise the alarm when it does not. Each has its own page, and each gives you the same two facts: when it last ran, and what happened.
Where to find it
| Screen | Where it lives | What it is for |
|---|---|---|
Maintenance — /admin/maintenance | Settings → System → Maintenance | the clean-up sweeps |
Conformance — /admin/maintenance/conformance | Settings → System → Conformance | the checks that prove things work |
Each page has its own view permission.
Maintenance sweeps
The table lists each Sweep with its Interval, whether it is Enabled, its Last run, its Last success and its Next due. A sweep that is due says due now; one retrying after a failure says so.
| Result | What it means |
|---|---|
| OK | it ran and finished |
| no changes | it ran and there was nothing to do — not a failure |
| Failed | it ran and reported a failure |
| Already running elsewhere — skipped | another worker had it; it was not run twice |
A sweep that has never succeeded says has never succeeded yet rather than showing a blank. Every run is recorded in the system event log.
Run now runs one immediately, whatever its schedule.
Conformance runners
A conformance runner is a background check that proves a subsystem still works: the phone stack, mail, the gateway, sign-in, integrations. It runs on a schedule and notifies operators when something breaks. The point is that a failure announces itself, instead of waiting to be discovered by a person trying to use the thing.
Each card shows the runner, its state, how many Checks it ran, and — when something failed — the First failure in words.
| State | What it means |
|---|---|
| Passing | every check passed |
| Failing | at least one check failed; the card names the first |
| Skipped | it did not apply, and the card says why |
| Never run | no run recorded yet |
Run history lists past runs with their Trigger — scheduled or manual — their Started time and their Result, so a check that passes most of the time and fails on Tuesdays is visible as a pattern rather than as one bad card.
Run now starts a runner by hand. It warns you that this can take a while and that the card refreshes when it finishes. If the runner is already running, it says so rather than starting a second copy.
All runners passing or skipped is the healthy summary. When some are failing, the header says how many.