Cairn
NousResearch/hermes-agent

Cron reminders lost when origin channel deleted

Cluster 54329 · cron. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

A bug was identified where cron reminders with deliver=origin are silently dropped if the target thread or channel is no longer accessible. Related work proposes and implements redirecting such stale deliveries to a parent or home channel instead.

Open issues1

  • Issue#54329[Bug]: deliver=origin cron reminders are silently dropped when the origin thread/channel is deleted or inaccessible

Open PRs2

  • PR#54341fix(cron): redirect delivery to home channel when origin target is deleted (#54329)
  • PR#54598feat(cron): redirect stale-target deliveries to parent/home channel
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/54329.json
cluster/54329.md