Gateway: secondary profile session deletion affecting launch profile session ids
Cluster 140744. Data as of
Nothing open on GitHub. Fix merged in #140787 on 18 Oct 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 #140787. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #140787. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members appear to concern a multiplexed gateway in which deleting or pruning a session in a secondary profile may cause the launch profile to keep refusing that session id. Two items are fix-oriented changes that mention keeping the routing fence separate from the launch profile and keying retirement by profile, but their outcomes are not stated here.
Open issues0
Open PRs0
Fixes on record
-
#140787 fix(gateway): a prune is not a permanent tombstone, and retirement is keyed by profile (LC-25, LC-26)
files:
gateway/platforms/api_server.py,gateway/platforms/api_server_authority_runs.py,gateway/platforms/api_server_memory_sessions.py,gateway/platforms/api_server_response_admissions.py,gateway/platforms/api_server_runs.py,gateway/session_api.py,gateway/session_api_turn.py,gateway/session_mutations.py,gateway/session_persistence.py,hermes_state_gateway.py,hermes_state_mutation_retirement.py,tests/gateway/test_api_server_memory_sessions.py,tests/gateway/test_delete_secondary_profile_multiplex.py,tests/gateway/test_derived_generation_after_sweep.py,tests/gateway/test_secondary_route_fence_scope.py,tests/hermes_state/test_retired_fence_outlives_horizon.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#140745 fix(gateway): keep a secondary profile's routing fence out of the launch profile's sessions · superseded by another PR →
#140787,#140762
Closed issues · 1
- Closed#140744Multiplexed gateway: deleting or pruning a session in a secondary profile makes the launch profile refuse that id for good
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
- #140787
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Oct 2026