Gateway bot mailbox receipt handling: stale pins and repeated scan warnings
Cluster 139138. Data as of
Nothing open on GitHub. Fix merged in #139648 on 16 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 #139648. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #139648. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members concern Discord/bot-mailbox receipts in the gateway, specifically receipts with an ambiguous status from permission_denied being rejected as an unknown schema on each scan. Two related pull requests propose handling leftover or stale bot receipt pins differently, by clearing them or skipping them quietly; their outcomes are not stated in the titles.
Open issues0
Open PRs0
Fixes on record
-
#139648 fix(gateway): clear stale Bot receipt pins whose admission never committed
files:
gateway/session_bot.py,gateway/session_bot_mailbox.py,tests/gateway/test_bot_receipt_pin_fifo.py,tests/gateway/test_bot_receipt_stale_pin.py
1 PR closed without merging
From the close comments: other 1
-
#139159 fix(gateway): skip refusal-left bot mailbox pins quietly instead of warning on every scan · other →
#139471,#139138,#134889
Closed issues · 1
- Closed#139138Discord/bot-mailbox receipts with status ambiguous from permission_denied are rejected as unknown receipt schema on every gateway scan
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
- #139648
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Oct 2026