Gateway busy follow-up ownership bug fix

Cluster 120999. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #121728 on 24 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #121728, then check it covers your case.

A bug where a busy follow-up queued at the end of a turn is left without an owner. These items describe the problem report and related fix attempts.

Open issues0

No open issues.

No open pull requests.

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

#121728 fix(gateway): start a busy follow-up that the finishing turn left without an owner

merged to main

files: contributors/emails/[redacted:email], gateway/platforms/base.py, tests/gateway/test_busy_followup_after_session_release.py, tests/gateway/test_busy_followup_guard_release.py

From the close comments: merged via another change 1

#121003 fix(gateway): a busy follow-up queued as the turn ends is no longer left without an owner · merged via another change → d350422, #121728

Closed issues · 1

Closed#120999[Bug]: Busy follow-up queued as the previous turn ends is left with no owner and runs after the next message

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.

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

The same facts, typed.