No more release of 6.2 planned, fix will be available through the other live releases.
Steps to reproduce:
1. Trigger any session
2. Observe Sessions section in Cloud Diagnostics Dashboard for the Project session that was triggered
Actual result: Two sessions appear, one with the actual duration of the session and another one with 0ms duration Expected result: One session appears with the actual duration of the session
Reproducible with versions: 6000.2.0b7
Tested on (OS): macOS Sequoia 15.5 (Intel)
Note: 0ms duration session start and end time is always the most recent one so it appears first in the Session list
Prioritise and Follow this issue
Have a workaround or additional info about this issue?