No laps were detected in my session

The session recorded, but it shows no laps. For phone GPS, RaceBox, and GoPro sessions, lap detection needs you to cross the start/finish line repeatedly with a usable GPS trace — one of those two things is missing. MyChron/AiM sessions work differently — see the last item below.

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. No curated start/finish line for this circuit. Today, only South Garda has a real, surveyed start/finish line — every other circuit, known or not, falls back to using wherever your GPS first got a lock as the start/finish point. If that happened before you reached the track (e.g. still in the paddock), you may never cross it again, and no laps will be detected.
6. MyChron/AiM session with no lap markers. MyChron sessions get their laps from the logger's own recorded lap markers, not from LapperSnapper's GPS trace — phone mounting has no effect here. If a MyChron session shows no laps, the logger itself didn't record any (check its lap-timing source/trigger).

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.