fix: session idle timestamp correction #1428
Merged
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.
In https://posthoghelp.zendesk.com/agent/tickets/16379 we see a session that emits zero events for > 10hrs and so doesn't trigger idle detection
when the session returns we correctly flushed only the session idle event and started a new session
but!
the session idle event has as its timestamp the point it was detected making for an 10hr+ session with 10 hours of inactivity
Since we know the threshold and the time of last activity we can correct the timestamp of the event before emitting it
tested locally and can see sessionIdle not being emitted at the time it was captured