fix(telegram): make polling conflict retryable with longer backoff - #23806
Closed
im-kris wants to merge 1 commit into
Closed
fix(telegram): make polling conflict retryable with longer backoff#23806im-kris wants to merge 1 commit into
im-kris wants to merge 1 commit into
Conversation
When the gateway restarts, Telegram may take longer than 30s to release the old getUpdates session. Previously the adapter gave up permanently after 3x10s retries (retryable=False), leaving the platform dead until manual restart. Raise retries to 5x20s and mark the error retryable so the background reconnection loop keeps trying until the session expires.
alt-glitch
added
type/bug
1 task
Closed
3 tasks
Contributor
|
Closing in favor of #25630 (more thorough fix for the same #23783 family). Your tactical patch (3→5 retries, 10s→20s backoff, retryable=True) doesn't address the worst bug in that area: when the retry's own #25630 fixes both stages: (1) the 409 window timing, and (2) the silent limbo after a failed retry — by scheduling a self-rescheduling attempt instead of dead-ending. Thanks for opening the conversation on #23783. |
This was referenced Aug 3, 2026
Closed
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
3 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.
Issue: Telegram getUpdates session survives the old gateway process on
the server side for an unknown grace period. During that window every
new getUpdates call gets 409 Conflict. The old code retried 3×10s and
then gave up permanently (retryable=False), requiring manual restart.
Fix: extend retries to 5×20s and mark the error retryable so the
background reconnection loop keeps trying if needed.
Closes #23783