The observed behavior is expected in some scenarios. Session lifecycle events, particularly Session End, depend on the application being able to send the event before shutdown. If the Game/Runtime is closed, terminated, crashes, or otherwise exits before the event is transmitted, the end-of-session record may be delayed until the next launch or may not be reflected immediately in the dashboard.
Because of this, log ordering and completeness for session end events may not always exactly match the sequence of user actions in real time.
We will review the documentation to clarify how session lifecycle events are collected, transmitted, and when delayed or missing Session End entries can be expected.