Repository navigation
Harden analytics SDK recovery - #105
Merged
Merged
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
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.
The browser SDK could permanently stop fetching configuration after four transient failures, treated HTTP 408 as permanent, and depended exclusively on
crypto.randomUUID(). Queue saturation was also invisible when no replaceable page update remained.This change restores configuration recovery when the browser comes online, applies bounded jitter and
Retry-After, safely creates UUID v4 identifiers withcrypto.getRandomValues()when needed, contains SDK errors so they cannot affect the host page, and adds opt-in reason-code diagnostics. Late recovery attributes only the current tagged page and never revives expired conversions.Validation:
9ed97380bc9d7a0f(8.0 KB / 3.2 KB gzip)