-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
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
feat: warn when distinct id invalid for replay #1277
feat: warn when distinct id invalid for replay #1277
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Size Change: +626 B (+0.06%) Total Size: 1.11 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we drop the events or is that too much?
well, we're going to drop them at capture, and return a 400 (since the last couple of days changes) so I think we're ok with a log error to point someone at as well currently this is only one customer, so even though it's pretty high volume from them, they seem to track latest version, so this will maybe help them understand what is happening 🙈 |
see https://posthog.sentry.io/issues/5544450836/?query=is%3Aunresolved+issue.priority%3A%5Bhigh%2C+medium%5D&referrer=issue-stream&statsPeriod=1h&stream_index=2
it's all one customer but we should warn in this scenario