fix(tools): retry Discord send on 429 rate-limit (#44468) - #44558
Closed
kyssta-exe wants to merge 1 commit into
Closed
fix(tools): retry Discord send on 429 rate-limit (#44468)#44558kyssta-exe wants to merge 1 commit into
kyssta-exe wants to merge 1 commit into
Conversation
alt-glitch
added
type/bug
Collaborator
Contributor
Author
1 task
19 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #44468. Adds retry logic with exponential backoff for Discord 429 rate-limit errors during multi-chunk message delivery. Previously a 429 on any chunk would abort the loop and silently drop all remaining chunks. Now each chunk is retried up to 3 times with delay (honoring Discord's retry_after when present, falling back to exponential backoff capped at 5s). This matches the existing Telegram retry behavior in _send_telegram_message_with_retry.