Feed status

What the lights mean

Green is within its expected interval. Amber is late enough to watch. Red needs investigation. Grey means no evidence is available yet.

Every card follows the evidence from left to right. A worker light proves that stage is completing successful loops; a backlog light proves work is not accumulating behind it. “Applicable update” means the feed changed at least one GRM service, rather than merely supplying a message. Quiet low-volume feeds are not failed simply because they have no new raw message.

Continuous-feed pending counts are capped at 1,000 to keep this ten-second view inexpensive. A healthy LINX restart deliberately reviews retained evidence for the current railway day; the card identifies this positive recovery separately and watches recent replay progress instead of treating the input's original age as time spent waiting. Schedule reports its latest daily publication input because other weekdays deliberately remain unshaped. The shared delivery chain is part of the overall light: live evidence is not considered healthy if operational interpretation or map materialisation has stopped.

Number help

Last successful activity

Age of the latest successful acquisition checkpoint. It proves the source session is functioning; it does not prove that a useful railway update was received.

Latest retained input

Age of the newest source message safely stored by GRM. TRUST and TD are expected to remain fresh; silence can be legitimate for Darwin, VSTP and LINX.

Latest publication input

Age of the timetable source used by the current published schedule model. Schedule publication is daily rather than continuous.

Worker completed / successful loop

Age of the latest error-free loop through that worker. A current worker can still have a backlog, which is reported separately.

Pending raw rows

Source messages durably stored but not yet shaped. Counts display at most 1,000+ so this frequently refreshed diagnostic stays inexpensive.

Oldest pending

How long the oldest unshaped source message has waited. This age, rather than a momentary small count, controls the processing traffic light.

Replay progress

Age of the latest successful LINX replay batch. A recent value means the restart recovery is actively moving; it turns amber or red if progress stops.

Rows left to review

Retained current-day LINX messages deliberately placed back through shaping after a restart. They are recovery work, not evidence that acquisition failed, and the count falls as the review completes.

Oldest retained input

When the oldest replayed LINX message was originally acquired. It describes the coverage being recovered, not how long that message has been stuck.

Ready to apply

Shaped evidence with an unambiguous live GRM service match that is waiting for application. Its oldest age contributes to the application traffic light. Unavailable means this optional diagnostic failed; the rest of the feed chain remains visible.

Awaiting live service

Retained Darwin forecasts whose UID and service date have no live presentation service yet. Darwin does not create services; TRUST activation may make these applicable later. They are not treated as a processing failure and old rows are cleaned up.

Match conflicts

Darwin evidence for which a live UID/date exists but the origin differs, or more than one exact service match exists. GRM deliberately refuses to guess. These are investigation leads, not a whole-feed outage.

Latest applicable update

Age of the last feed update that affected at least one matching GRM service. Provider traffic alone does not advance it.

Browser refresh interval

How often this page requests a fresh status snapshot from the live database.