Prevent infinite retry loops when the Web SDK encounters clearly invalid tokens #4415
Conversation
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
Contributor
|
Web SDK Sample Build link |
Contributor
|
Lightbeam link |
cdhanna
approved these changes
Nov 17, 2025
molaycule
deleted the
issue/4391-websdk--infinite-retry-when-token-is-clearly-broken
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ticket
#4391
Brief Description
This update prevents the Web SDK from entering an infinite retry loop when a token is clearly invalid. Specifically, the requester now detects known authentication failures (
InvalidCredentialsError,InvalidRefreshTokenError,TokenValidationError) and skips refresh attempts in those cases. This ensures the SDK doesn’t repeatedly retry against unrecoverable auth states and instead fails fast, improving stability and avoiding unnecessary network traffic. The changelog has also been updated to document this fix.Checklist