Cairn
NousResearch/hermes-agent

Slack Socket Mode zombie session reconnect handling

Cluster 85574 · gateway. 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 a scenario where the Socket Mode watchdog cannot recover from a broken or closed aiohttp session because reconnection reuses the same defunct client. The proposed fixes involve rebuilding the AsyncApp and its clients rather than reusing the existing broken ones.

Open issues1

  • Issue#85574Slack Socket Mode watchdog can't self-heal a zombie aiohttp session — reconnect reuses the same broken client

Open PRs1

  • PR#85660fix(slack): rebuild AsyncApp and clients on Socket Mode watchdog restart

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #96113 fix(slack): escalate closed-session Socket Mode wedge to adapter rebuild · superseded by another PR → #85660, #95516, #95527, #96069, #85574
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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/85574.json
cluster/85574.md