Cairn
NousResearch/hermes-agent

Cron monitor no_change ticks affecting failure state handling

Cluster 140178 · 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 concern how cron monitor ticks, specifically no_change and suppressed ones, are treated with respect to a job's failure state. One item reports that no_change ticks are treated as recoveries (resolving incidents and resetting failure_streak), and the other two titles propose treating such ticks as neutral.

Open issues1

  • Issue#140178[Bug]: monitor no_change ticks resolve cron failure incidents and reset failure_streak, defeating failure_repeat_alert_hours

Open PRs1

  • PR#140193fix(cron): a monitor no_change tick is neutral, not a recovery

1 PR closed without merging

From the close comments: other 1

  • #140200 fix(cron): a suppressed monitor tick is neutral for the job's failure state · other → #140893, #140849, #140808, #140236, #139530
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/140178.json
cluster/140178.md