V2: Introduce cache cap, backoff when retrying previously failed events#286
Open
kkostov wants to merge 9 commits into
Open
V2: Introduce cache cap, backoff when retrying previously failed events#286kkostov wants to merge 9 commits into
kkostov wants to merge 9 commits into
Conversation
Joypeffpwpc
reviewed
May 13, 2026
0a5d30c to
abafe2a
Compare
abafe2a to
530f576
Compare
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.
This PR fixes #284 by capping the maximum number of events we keep in cache and introducing a back-off retry mechanism for previously failed batches.
TelemetryManagerConfigurationhas been extended to allow apps to configure this behaviour as needed:cacheLimitInt10_000transmitIntervalTimeInterval10maxBackoffIntervalTimeInterval300Fixed a possible race where during
didEnterForeground,signalCacheis updated on the main queue while events can be pushed and popped from other queues.If the SDK gets one of the following response codes when transmitting events, it will not attempt to send these events again (they will be permanently dropped): 400, 401, 403, 404, 413, 422, 501, 505.