Document replay.stop({ flush: false }) option#18759
Merged
Merged
Conversation
Documents the new option for skipping the final flush when stopping Session Replay, for consent-withdrawal (GDPR) flows. Depends on getsentry/sentry-javascript#22300 (targeting 10.67.0).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
andreiborza
approved these changes
Jul 20, 2026
logaretm
marked this pull request as ready for review
July 20, 2026 14:13
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
2 participants
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.
Documents the new
replay.stop({ flush: false })option that stops Session Replay without sending the pending segment, for consent-withdrawal (GDPR) flows.Depends on getsentry/sentry-javascript#22300, which adds the option. Assuming it lands next, the feature ships in 10.67.0, which is what the
AvailableSincetag reflects. If the SDK release ends up being a different version, the tag needs updating before this merges.