Cairn
NousResearch/hermes-agent

Cron tick false failure reports during gateway restart

Cluster 99120 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items address a bug where cron ticks queued during a gateway restart are incorrectly reported as failed. The fixes aim to suppress or prevent misleading failure delivery in that scenario.

Open issues1

  • Issue#99120fix(cron): avoid misleading failure delivery for queued ticks during gateway restart

Open PRs1

  • PR#99154fix(cron): stop gateway restarts from falsely failing queued ticks

1 PR closed without merging

From the close comments: won't fix / by design 1

  • #99184 fix(cron): suppress misleading failure delivery for queued ticks during restart · won't fix / by design → #99184
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

Subsystem
cron
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/99120.json
cluster/99120.md