Discord slash-command sync timeout under rate-limit pressure
Cluster 16713. Data as of
Nothing open on GitHub. Fix merged in #17029 on 28 Apr 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 #17029. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #17029. That is separate from the fix event. - Still open
- Nothing open on GitHub.
All three members concern the Discord slash-command sync timeout (_safe_sync_slash_commands), which has a 30s budget described as too tight after pruning under rate limits. Two pull requests reference #16713 and propose different adjustments: widening the timeout to 600s or scaling it to the number of writes.
Open issues0
Open PRs0
Fixes on record
-
#17029 fix(discord): widen slash-sync timeout to 600s under rate-limit pressure (#16713)
files:
gateway/platforms/discord.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#16739 fix(discord): scale slash sync timeout to actual write count (#16713) · superseded by another PR →
#17029
Closed issues · 1
- Closed#16713_safe_sync_slash_commands times out under post-prune rate-limit pressure (30s budget too tight)
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
- #17029
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 28 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.