Schedules and Findings

Schedules and Findings

Recurring monitors and aggregated quality issues in Mission Control.

Schedules

Turn any job into a loop (5 min – 6 h). Single-flight: a due schedule won’t start if another job is already running.

Typical uses:

Interval	Job
Every 15 min	Smoke
Hourly	Site audit
Daily	TLS check
Custom	Flow / route-sweep / API / realtime / vitals

Add/remove from the Schedules panel or ⌘K. Local spec paths must stay inside the repo; URLs pass target policy.

API: GET/POST/DELETE /api/dashboard/schedules[/{id}] — Dashboard API.

Enterprise schedules persist in SQLite (reports/mission-control.db or ZYVOR_STATE_DB) and reject raw secrets in params.

Findings

Findings aggregates issues from quality jobs (audit failures, probe hits, flaky offenders, etc.) so you don’t dig through every run row.

Pair with:

• QA Runs — sparkline + expandable history + JSON export
• Test health — worst offenders (fail count / % / flaky badge)
• Videos — recorded journeys + zip download

Related

Using the Dashboard · Probes and Audits · Common Workflows · Enterprise