We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, if you look e.g. at this issue: https://sentry.sentry.io/replays/04147ee7b3684015a60d6d951f4a4303/?project=11276&query=&referrer=%2Freplays%2F&statsPeriod=7d&t_main=errors&yAxis=count%28%29 you can see that the error gets the replay_id added even though the session is for sure expired.
We should check in the error handler if the session is expired before attaching the replay_id.
The text was updated successfully, but these errors were encountered:
replay_id
fix(replay): Ensure replay_id is not captured when session is expir…
618e992
…ed (#9109) Closes #9106
7adf5db
mydea
Successfully merging a pull request may close this issue.
Currently, if you look e.g. at this issue: https://sentry.sentry.io/replays/04147ee7b3684015a60d6d951f4a4303/?project=11276&query=&referrer=%2Freplays%2F&statsPeriod=7d&t_main=errors&yAxis=count%28%29 you can see that the error gets the replay_id added even though the session is for sure expired.
We should check in the error handler if the session is expired before attaching the replay_id.
The text was updated successfully, but these errors were encountered: