Slack handoff session key lost on gateway restart
Cluster 111896. Data as of
Nothing open on GitHub. Fix merged in #112222 on 16 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #112222. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where Slack DM or thread handoffs are assigned a different session key after a gateway restart, orphaning the original session and losing context. The members cover the issue report and related fix attempts targeting this behavior.
Open issues0
Open PRs0
Fixes on record
-
#112222 fix(gateway): Slack /handoff threads keep their session across gateway restarts (#111896, supersedes #111899)
files:
gateway/run_startup.py,plugins/platforms/slack/adapter.py,tests/gateway/test_handoff_thread_session_key.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#111899 fix(gateway): preserve Slack DM handoff session keys · merged via another change →
9a41a8b,#112222
Closed issues · 1
- Closed#111896Slack: same thread rebinds to a different session key after gateway restart (dm vs thread layout), orphaning the handoff-ed session and losing context
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.00means 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 LabAt a glance
- Merged PRs
- #112222
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Sep 2026