Cairn
NousResearch/hermes-agent

Kanban notifier failure isolation in gateway subscriptions

Cluster 59269 · gateway. Data as of

Nothing open on GitHub. Fix merged in #72236 on 26 Jul 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #72236. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #72236. That is separate from the fix event.
Still open
Nothing open on GitHub.

The members appear to concern the gateway's kanban notifier, where one bad delivery is described as jamming notifications and masking the underlying error. Two titles propose changes to isolate failures per subscription, and one also mentions a cursor snap at creation.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #72236 fix(gateway): isolate kanban notifier failures + cursor snap at creation (salvage #59278, #62712, #63001)

    merged to main

    files: contributors/emails/[redacted:email], gateway/authz_mixin.py, gateway/kanban_watchers.py, hermes_cli/kanban_db.py, tests/gateway/test_kanban_notifier.py, tests/gateway/test_kanban_notifier_zero_sub_gate.py, tests/gateway/test_multiplex_profile_authz.py, tests/hermes_cli/test_kanban_core_functionality.py, tests/hermes_cli/test_kanban_count_notify_subs.py, tests/hermes_cli/test_kanban_notify.py, tests/tui_gateway/test_kanban_notify_poller.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #59278 fix(gateway): isolate per-subscription failures in kanban notifier · merged via another change → #72236, #59269
Closed issues · 1
  • Closed#59269Kanban notifier jams permanently on one bad delivery — masks the real error and blocks all notifications
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
gateway
Merged PRs
#72236
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
26 Jul 2026

For your agent

The same facts, typed.

cluster/59269.json
cluster/59269.md