Cairn
NousResearch/hermes-agent

Cron ticker silent failure detection and resilience

Cluster 36854. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes all concern the cron ticker thread dying or stalling silently without logging errors, triggering alerts, or recovering automatically. Work spans detection, watchdog supervision, exception hardening, heartbeat tracking, and lock-bound stall prevention.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: partial fix 1 · superseded by another PR 1

  • #36945 fix(gateway): keep cron ticker alive after tick failures · superseded by another PR → #38718
  • #38718 fix(cron): NameError get_fallback_chain + silent ticker death + tick() blocks (#36734 #36854 #37312) · partial fix → #37312, #39008, #36734, #36854
Closed issues · 1
  • Closed#36854Cron ticker silently dies when prompt-injection scanner blocks a job — entire cron scheduler stops until gateway restart
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.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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/36854.json
cluster/36854.md