Expose cron lateness and catch-up run timing in UI
Cluster 99879. Data as of
Nothing open on GitHub. Fix merged in #100445 on 1 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #100445. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address surfacing missed-fire catch-up lateness information in cron list and status views, ensuring that runs dispatched late after downtime are tagged with scheduled vs actual time and visible in the UI.
Open issues0
Open PRs0
Fixes on record
-
#100445 fix(cron): surface missed-fire catch-up lateness in hermes cron list/status
files:
cron/jobs.py,hermes_cli/cron.py,tests/cron/test_dispatch_lateness_stamp.py,tests/hermes_cli/test_cron_dispatch_visibility.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#99919 fix(cron): tag catch-up dispatches with scheduled vs actual time and lateness so late runs surface in UI · superseded by another PR →
#100445,#99879
Closed issues · 1
- Closed#99879Routines run late after gateway downtime with no missed-run status
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #100445
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 1 Sep 2026