Fleet defaults

Editing the default schedule every project inherits · pick a project in the switcher to override it

scheduler healthy · 0s ago
Fleet defaults Changes here apply to all 1,284 projects except the 38 that carry their own override.
Jobs enabled
5/ 6
1 paused
cron jobs on this scope
Runs per day
310
per project, all jobs combined
tighter cadence = more runs
Next run
in 2m 14s
Console sweep
soonest scheduled job
Fleet API budget
62% used
15,408 of 25,000 PSI calls/day

Job schedule

cadence per job · all times UTC 0 overridden on this scope
JobCadenceRuns / dayNext runSource
A tighter cadence costs probe capacity and API quota. The budget meter above moves as you change these.

Thresholds & retention

scoped to fleet defaults
alerts when field p75 exceeds this for 60m
alerts when fire rate drops below this for 10m
flags a variant as failing below this
raw captures are the largest store
Respect quiet hours
no paging 22:00–07:00 UTC · jobs still run
Thresholds apply to this scope only — projects that inherit keep the fleet default.

Projects with overrides

38 of 1,284
Everything else inherits the fleet default.

Scheduler health

Runs completed · 24h
across this scope
398,240
Runs skipped
previous run still in flight
1,204
Runs failed
probe timeout or 5xx
316

Skips mean the cadence is too tight. A console sweep that takes 3.2s can't run every 2 minutes on a project with 6 URLs — the scheduler drops the overlap rather than queueing it.

Prototype · figures are sample data for layout review, not production telemetry.