Cairn
NousResearch/hermes-agent

Cron reclaimed executions missing alerts and incidents

Cluster 108802 · 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 issues address a gap where reclaimed (unknown) cron executions produce no incident, no failure delivery, and no alert. The work focuses on surfacing these silent reclaimed executions through proper alerting and incident reporting.

Open issues1

  • Issue#108802[cron] reclaimed execution (unknown) is silent: no incident and no failure-deliver

Open PRs1

  • PR#108806fix(cron): alert on reclaimed executions

1 PR closed without merging

From the close comments: duplicate 1

  • #108920 fix(cron): surface reclaimed (unknown) executions through incident + failure lane · duplicate → #108806, #108802
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/108802.json
cluster/108802.md