Copyright © 2026 Unity Technologies
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.
Steps to reproduce:
Actual results: not all the actions are reflected correctly, "Session End" is usually missing until the next session becomes active, logs duplicate or have wrong order
Expected results: logs correctly reflect all the performed actions
Reproducible with versions: 6000.2.14f1, 6000.3.5f1, 6000.4.0b4, 6000.5.0a4
Can’t test with versions: 6000.0.66f1 (diagnostics were introduced in 6.2)
Tested on (OS): Windows 11
Notes:
Issues you vote on will appear here