Symptom
Unexpected connection interruption or recovery
Possible causes
A service/network interruption can leave an incomplete Session without a trusted finish.
Check in this order
- Check current telemetry separately from stored Session status.
- Inspect Interrupted in Sessions after recovery.
- Keep the approximate time and device/network context for support.
Safe corrective action
Reconnect safely. Mark an orphaned Session incomplete only through its explicit recovery action.
Verify recovery
New telemetry is fresh and the old record remains honestly incomplete rather than a fabricated race result.
Related manual
When to contact support
If these checks do not explain or resolve the symptom, prepare focused feedback or email support@lap-mind.com. Include version, device, console, approximate time, settings and expected versus observed behaviour. Do not include tokens, real console IPs or private captures in a public report. Agree a private evidence transfer first.