Skip to content

Conversation

@harshit078
Copy link
Contributor

@harshit078 harshit078 commented Jan 13, 2026

This PR distinguishes replays that get dropped due to session length vs. transport/ratelimit reasons in the client report.

depends on #18901
closes #18316

@harshit078 harshit078 marked this pull request as ready for review January 13, 2026 20:34
@harshit078 harshit078 requested a review from a team as a code owner January 13, 2026 20:34
@chargome chargome self-assigned this Jan 19, 2026
Copy link
Member

@chargome chargome left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @harshit078 thanks for contributing! For the lack of better options in the drop reasons (see https://develop.sentry.dev/sdk/telemetry/client-reports/#envelope-item-payload) I think the most fitting is still send_error in this case.

cursor[bot]

This comment was marked as outdated.

@chargome chargome changed the title feat(replay): Introduce ReplayDurationLimitError and enhance error ha… feat(replay): Update client report discard reason for invalid sessions Jan 20, 2026
@chargome chargome marked this pull request as draft January 20, 2026 15:38
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

@chargome chargome marked this pull request as ready for review January 23, 2026 12:04
@chargome chargome requested a review from andreiborza January 23, 2026 12:06
Copy link
Member

@andreiborza andreiborza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, thanks for the contribution!

@chargome chargome merged commit a2f7fad into getsentry:develop Jan 23, 2026
188 checks passed
@harshit078 harshit078 deleted the fixing-outcome-flushing-replay branch January 23, 2026 13:09
nicohrubec pushed a commit that referenced this pull request Jan 23, 2026
This PR adds the external contributor to the CHANGELOG.md file, so that
they are credited for their contribution. See #18796

Co-authored-by: chargome <20254395+chargome@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Inaccurate outcome when flushing replays

3 participants