Cairn

Cron overdue job detection and display fixes

NousResearch/hermes-agent · cluster 114309

Data as of

Nothing open on GitHub. Fix merged in #114860. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #114860. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #114860. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests address the detection and surfacing of overdue cron jobs — where next_run_at is in the past — across the CLI status/list commands, dashboard, and Desktop. A related report describes a scheduler heartbeat failure leaving a job unfired with no overdue indication.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #114860 fix(cron): overdue next runs are labelled on status, list, dashboard and Desktop; status picks the soonest run by instant (#114309, #113874, salvage #112680, #114330)

    merged to main

    files: apps/desktop/src/app/chat/sidebar/cron-jobs-section.tsx, apps/desktop/src/app/cron/cron-job-model.test.ts, apps/desktop/src/app/cron/index.tsx, apps/desktop/src/app/cron/job-state.ts, apps/desktop/src/i18n/en.ts, apps/desktop/src/i18n/types.ts, apps/desktop/src/plugins/hermes-bots/cron-detail.test.tsx, apps/desktop/src/plugins/hermes-bots/cron.tsx, apps/desktop/src/sdk/index.ts, hermes_cli/cli_commands_mixin.py, hermes_cli/cron.py, hermes_cli/web_server_cron.py, tests/hermes_cli/test_cron.py, tests/hermes_cli/test_cron_status_next_run.py, tests/hermes_cli/test_web_server_cron_profiles.py, web/src/i18n/en.ts, web/src/i18n/types.ts, web/src/lib/api.ts, web/src/lib/cron-job.test.ts, web/src/lib/cron-job.ts (+2 more)

3 PRs closed without merging

From the close comments: merged via another change 2 · superseded by another PR 1

  • #114330 fix(cli): flag overdue next_run_at and stale ticker in cron status · merged via another change → 5179b51, #114860, #114309, #112680, #114330
  • #114357 fix(cron): flag overdue jobs in cron list/status next-run display (#114309) · superseded by another PR → #114328, #114330, #114309, #114357
  • #114443 fix(cron): surface past next_run_at as overdue across CLI and dashboard · merged via another change → 5179b51, #114860, #114309, #114330
Closed issues · 1
  • Closed#114309Cron: scheduler heartbeat dead since yesterday — recurring job sits with next_run_at ~7h in the past, no catch-up fire, no overdue indication
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Merged PRs
#114860
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/114309.json
cluster/114309.md