monthly · scheduled SLA 40d
Finder
DOWN
no heartbeat
0 probed · 0 found · 0 budget left
8 stations overdue · Finder no heartbeat
The clocks, and the locked doors.
Every dispatch station on collegedata.fyi, when it last ran on schedule, and what it found. If a step goes quiet, the lamp turns red — including the monthly search that sat idle from April to August 2026. Locked doors (Tableau, SharePoint IRM, SSO) ship in the next slice; this page is the clocks.
Dispatch board
monthly · scheduled SLA 40d
Stuck PDFs
DOWN
no heartbeat
0 stuck · 0 reprobed · 0 still stuck
monthly · scheduled SLA 40d
Landing hints
DOWN
no heartbeat
0 proposals · 0 promoted
daily · SLA 36h
Enqueue
DOWN
no heartbeat
0 queued · 0 skipped
every 30s
Process
OK
2 sec
queue 0 · 0 inserted · 0 events
daily · pending drain
Extract
DOWN
no heartbeat
1 pending · —
hourly · SLA 3h
Coverage
DOWN
no heartbeat
0 current · 0 stale
hourly · SLA 3h
Serving caches
DOWN
no heartbeat
refresh_public_serving_caches
monthly · scheduled SLA 40d
IPEDS probe
DOWN
no heartbeat
no new release
yearly · slate until a heartbeat
Schema
SLATE
no heartbeat
Do not infer vintage from git.
yearly · slate until a heartbeat
Scorecard
SLATE
no heartbeat
Do not infer vintage from git.
Manual sources (not on the strip): Directory enqueue — no heartbeat · Mirror ingest — no heartbeat
Methodology
Each station writes a public heartbeat when it starts and when it finishes. Lamps are computed at read time from the scheduled clock. A manual GitHub run cannot green a missing cron. If the scheduled heartbeat is older than the SLA, the lamp is red — including when a dispatch succeeded yesterday. Missing data is red, not gray.
This page is not coverage. Coverage asks whether we have a CDS. This board asks whether the machine is running. JSON snapshot: /pipeline-observation.json.