LapMind

LapMind Help

Timed elapsed messages do not occur

The race may not be recognised as timed, the interval may be Off, or the elapsed fact may be unavailable/stale.

0.7.2-beta37 · code95 · Development candidate, not released Public Beta. Physical PS5/PS5 Pro and sustained GT7 checks remain open.

Symptom

Timed elapsed messages do not occur

Possible causes

The race may not be recognised as timed, the interval may be Off, or the elapsed fact may be unavailable/stale.

Check in this order

  1. Check Timed-race announcements.
  2. Periodic defaults to five minutes; after-lap elapsed is a separate default-OFF switch.
  3. Confirm a timed race and real progress in its authoritative elapsed domain.
  4. A coincident selected Summary can cover elapsed at the boundary.

Safe corrective action

Choose the desired interval and observe a future milestone. Do not expect a catch-up burst after changing settings.

Verify recovery

A future qualified milestone is attempted; fixed-lap races should not gain timed periodic calls.

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.