fix(P13): route transient Segment send-loop errors off Sentry - #9406
Closed
eordano wants to merge 1 commit into
Closed
fix(P13): route transient Segment send-loop errors off Sentry#9406eordano wants to merge 1 commit into
eordano wants to merge 1 commit into
Conversation
UNITY-EXPLORER-P13 (637 evts/242 users — widest reach): "Segment error: Error
executing send loop (will retry): ClientError {...}". The Rust Segment SDK's
background send loop reports transient, self-recovering upload failures via
ErrorCallback, which called ReportHub.LogException → Sentry (error level). The
existing once-per-session guard still emitted one Sentry error per user. Route
"(will retry)" messages to LogWarning on ReportHandler.DebugLog (local log, never
Sentry); genuine non-transient Segment errors keep Sentry reporting. Removed the
now-unused ONCE_PATTERN_ALREADY_CAUGHT field. Report-noise reduction. Unverified.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Production evidence (decentraland Sentry, archive snapshot 2026-07-17):
- UNITY-EXPLORER-P13: 29 events / 15 users, last seen 2026-07-16
- UNITY-EXPLORER-JVR: 8 events / 1 users, last seen 2026-02-22
Member
Author
|
Superseded by #9420 — branch moved into the org repo so CI workflows get repository secrets. |
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
1 participant
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.
UNITY-EXPLORER-P13 (637 evts/242 users — widest reach): "Segment error: Error executing send loop (will retry): ClientError {...}". The Rust Segment SDK's background send loop reports transient, self-recovering upload failures via ErrorCallback, which called ReportHub.LogException → Sentry (error level). The existing once-per-session guard still emitted one Sentry error per user. Route "(will retry)" messages to LogWarning on ReportHandler.DebugLog (local log, never Sentry); genuine non-transient Segment errors keep Sentry reporting. Removed the now-unused ONCE_PATTERN_ALREADY_CAUGHT field. Report-noise reduction. Unverified.