Bounding watch-notification requeue loops after refused gateway admission
Cluster 140899 · gateway. Data as of
Nothing open on GitHub. Fix merged in #141926 on 20 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 #141926. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #141926. That is separate from the fix event. - Still open
- Nothing open on GitHub.
One bug report describes watch-match notifications being requeued indefinitely at a 2 s drain when admission is refused, with no backoff, cap, or TTL. Two fix PRs address this by adding backoff or bounding requeues; one is broader, covering other background deliveries (async, cron, Bot Chat, DM). Titles alone do not show whether these changes are merged or effective.
Open issues0
Open PRs0
Fixes on record
-
#141926 fix: background deliveries the unified gateway refuses settle instead of looping (watch, async, cron, Bot Chat, DM)
files:
apps/desktop/src/components/assistant-ui/thread/assistant-message.tsx,apps/desktop/src/i18n/ar_assistant.ts,apps/desktop/src/i18n/de.ts,apps/desktop/src/i18n/de_notices.ts,apps/desktop/src/i18n/en.ts,apps/desktop/src/i18n/en_error_layers.ts,apps/desktop/src/i18n/es.ts,apps/desktop/src/i18n/es_notices.ts,apps/desktop/src/i18n/fr.ts,apps/desktop/src/i18n/fr_notices.ts,apps/desktop/src/i18n/ja.ts,apps/desktop/src/i18n/ja_notices.ts,apps/desktop/src/i18n/ru.ts,apps/desktop/src/i18n/ru_notices.ts,apps/desktop/src/i18n/zh-hant_assistant.ts,apps/desktop/src/i18n/zh.ts,apps/desktop/src/i18n/zh_notices.ts,apps/desktop/src/lib/error-surface.test.ts,apps/desktop/src/lib/error-surface.ts,contributors/emails/[redacted:email](+34 more)
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#140911 fix(gateway): bound watch-drain requeues with backoff after refused admission · superseded by another PR →
a9b2968,#141926,#140899,#141562,#142115
Closed issues · 1
- Closed#140899[Bug]: Watch-match notification requeued forever at the 2 s drain when admission is refused (no backoff/cap/TTL)
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
- Subsystem
- gateway
- Merged PRs
- #141926
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Oct 2026