Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insights: expired events in a batch make the server decline the whole batch #192

Closed
VladislavFitz opened this issue Sep 15, 2021 · 0 comments 路 Fixed by #200
Closed

Insights: expired events in a batch make the server decline the whole batch #192

VladislavFitz opened this issue Sep 15, 2021 · 0 comments 路 Fixed by #200
Assignees

Comments

@VladislavFitz
Copy link
Contributor

VladislavFitz commented Sep 15, 2021

Describe the bug 馃悰

The server doesn't accept the Insights events older than 4 days.
If a batch contains "expired" events and fresh events, they will all be declined by the server.

To Reproduce 馃攳

Steps to reproduce the behavior:

  1. Track a few Insights events assigning them more than 4 days old timestamps
  2. Track a few Insights events with real-time timestamps
  3. Flush the events
  4. The server will decline the events batch

Expected behavior 馃挱

Before sending the events batch to the server, the expired events must be excluded.

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 a pull request may close this issue.

1 participant