The session recorded, but it shows no laps. Lap detection needs you to cross the start/finish line repeatedly with a usable GPS trace — one of those two things is missing.

Common causes

1. The session never left the paddock. Driving to scrutineering and back contains no laps. Check the Map tab — if the trace never goes around the circuit, that's the answer.
2. Only one flying lap. Detection needs complete laps — an out-lap straight into the pits may yield none.
3. Poor GPS. A phone in a pocket, under a seat, or with battery-saver on produces a trace too rough to detect crossings. See GPS accuracy tips for recording.
4. GPS dropout at the line. If the signal cut out right at a lap boundary, that lap's time may be missing or marked approximate.
5. Unknown or temporary circuit. At tracks the app doesn't recognise, detection falls back to your driving pattern alone — usually fine, but unusual layouts can defeat it.

What to try

• Open the Map tab and sanity-check the trace — it usually makes the cause obvious.
• Next session: mount the phone with sky view, keep the screen on, or use a RaceBox/MyChron as the source.

If a session with a clean, complete trace still shows no laps, we want to see it — Contact support and attach the session file.