Why does it say that?

Confidence chip

Top bar of the session and compare pages; the badge in the session list. Hover it (long-press on the phone) for the detection notes below.

High confidence

Three or more valid laps whose lengths agree within 10 %; or an iRacing file with at least one complete lap.

Medium confidence

Two or more valid laps whose lengths agree within 25 %.

Low confidence

Fewer valid laps, or lengths that disagree more than that.

Single lap · unconfirmed

No repeated GPS crossing anywhere in the file. In the session list the badge reads Single lap, unconfirmed.

No GPS

Too few samples carry a position to detect laps.

Detection notes

The tooltip behind the confidence chip, and the Laps not counted list in the session-ready email. One or more of:

Reference point revisited ‹n›x (downsampled search); calibrated confirm radius entry=‹e›m/exit=‹x›m; estimated lap length ‹L›m from ‹r› raw crossings, ‹a› accepted after debounce.

Every GPS session. How the start/finish reference was found and how many passes through it were accepted as lap boundaries.

Low confidence: ‹n› valid lap(s), lap-distance variation ‹p›% — treat these lap times as approximate, not authoritative.

Added whenever the confidence is low.

No repeated GPS crossing found anywhere in this file — either a single-lap recording or a track loop this algorithm couldn't close. Reporting the full recorded span as one unconfirmed segment rather than a cross-validated lap.

Single lap · unconfirmed, when no point of the trace is revisited.

Found a candidate reference point (revisited ‹n›x in the downsampled search) but fewer than 2 clean crossings at any calibrated radius (tried …, best was entry=‹e›m/exit=‹x›m) — not enough to time a lap.

Single lap · unconfirmed, when a revisited point exists but the passes through it are not clean enough to time.

Only ‹k›/‹n› samples have GPS — can't detect laps.

No GPS.

Partial lap before the first confirmed reference-point crossing. / Partial lap after the last confirmed reference-point crossing.

The out-lap and the in-lap.

Lap distance ‹d›m deviates ‹p›% from the ‹L›m median — likely a missed or spurious crossing nearby, flagged rather than trusted.

A lap more than 25 % longer or shorter than the median lap; it is marked invalid (tag LOW).

Lap ‹n›: ‹d› m is ‹p›% of the ‹L› m reference lap — below the completeness floor (50%): a fragment between two crossings, not a complete lap. Kept as 'lap', marked invalid.

A lap under half the reference length.

Lap ‹n›: ‹t› s is ‹r›x the ‹T› s reference lap time — above the lap-time ceiling (1.5x): a full-distance lap that contains a stop or a long off. Kept as 'lap', marked invalid.

A lap over one and a half times the reference time.

Beacon markers present but disagree with GPS detection by more than 3s; treat lap boundaries as uncertain (‹u› of ‹n› .ldx marker(s) unmatched).

MoTeC, when an uploaded .ldx has manual markers that do not match the detected crossings.

Lap boundaries and numbers from the sim's own lap counter (LapDistPct / Lap), not the GPS heuristic.

Every iRacing session.

‹n› start/finish crossings → ‹m› complete lap(s).

Every iRacing session with at least one complete lap.

Sector positions from the sim's track distance (LapDistPct); metre readouts are GPS path distance.

Every iRacing session; also the note under the sector caption.

No LapDistPct wrap found — a single unconfirmed segment.

An iRacing recording whose lap counter never wrapped.

Recording begins ‹g› ms (‹f› of a lap) after the sim's crossing — lap anchored at the crossing using the sim's own lap timer (LapLastLapTime ‹t› s); the first ‹g› ms of S1 are from the sim's timer, not from a sample.

An iRacing recording started just after a start/finish crossing.

Lap table

Laps · ‹n› confirmed · ‹m› out/in

The table heading: complete valid laps, and the partial passes at either end.

S1–S‹n› · iRacing splits / S1–S‹n› · equal thirds

Where the sector columns' boundaries come from. Halves, quarters and so on name an even split with another count; file splits an uneven one.

· not computed for this session

The session predates display sectors and has not been recomputed; the columns show dashes.

lap numbers from the sim's counter · Sector positions from the sim's track distance (LapDistPct); metre readouts are GPS path distance

Under the caption of an iRacing session.

measured from the detected lap start, not the iRacing start/finish line

Under the caption of a session whose splits come from the file but whose laps were detected from GPS.

Sector positions from GPS path distance, measured from the detected lap start.

Under the caption of every non-sim session with display sectors.

‹n› checked lap(s) hidden by this filter — still selected

A filter is hiding a lap you had checked.

OUT · IN · UNCONF · LOW

Tags: out-lap, in-lap, unconfirmed single segment, invalid lap (or any lap in a low-confidence session).

Micro-sectors · ‹n› of ‹k› · equal fractions of the detected lap · the ideal lap's basis

The row opened with ▸ beside a lap number.

Ideal lap

Ideal ‹time› from ‹n› lap(s) at N=‹k› · ‹Δ› vs best · ‹s› seam(s) · approximate (low confidence)

The ideal line. Seams appear only when there are any; approximate only in a low-confidence session.

Computed from ‹k› micro-sectors; can be lower than the fastest sectors above added together.

Always under the ideal line.

No ideal lap: lap-detection confidence is ‹conf› — there are no trustworthy sector boundaries to compose from.

Sessions with no GPS or a single unconfirmed segment.

No ideal lap: no complete, valid lap with sectors in this session (in-laps, out-laps, unconfirmed segments and invalid laps are excluded by design).

No lap qualifies.

No ideal lap: no eligible lap has sector ‹k› of ‹n›. A missing sector is never treated as zero.

Every qualifying lap is missing the same micro-sector.

Charts and map

No channels selected — press 1–6 or use the rail.

Every channel switched off.

Toggling never resets scroll or zoom. Keys 1–6 toggle from anywhere.

Always, at the bottom of the channel rail.

‹Channel›: this logger has no ‹channel› channel

Tooltip on a rail entry shown as no data.

Select a lap to chart it.

A session with no chartable lap.

No GPS trace for the selected lap.

The track map, when the charted lap has no positions.

Magenta dot = detected start/finish. Rings track the hovered distance on any chart.

Always, under the track map.

Compare

Check two laps in the table — the first becomes the reference (white), the second the comparison (blue).

Fewer than two laps checked. One more to go. is added with one checked.

Δ time · green = L‹c› gaining on L‹r› · yellow = losing

The strip's header, always.

at ‹x› m · raw sample, not smoothed

The readout while the cursor is on a chart.

Hover any chart to pin the cursor across all of them and the map.

The readout with no cursor.

Maximum gain ‹Δ› s at ‹x› m (L‹c› vs session best L‹r›).

F1 mode, when the comparison lap is ahead somewhere.

F1 mode: L‹c› is never ahead of session best L‹r› at any point of the lap — there is no point of maximum gain to mark.

F1 mode, when it never is.

F1 mode · vs session best (neither lap is the session best)

The checkbox, disabled, when the best lap is not one of the pair.

Δ trace covers 0–‹x› m of a ‹y› m lap (shared axis stops where the shorter lap's data ends); the trace's last value is ‹Δ› s — Final above is from the two lap times.

The two laps' data do not cover the same distance.

Trace ends at ‹Δ› s; Final (‹Δ› s) is from the two lap times — the difference is resampling at the last grid point, not a timing discrepancy.

Full coverage, but the trace's last value and Final differ by more than 0.05 s.

L‹r› is ‹tag›; L‹c› is ‹tag› — an uncertain lap's Δ is measured on the session's median lap length and is approximate, not authoritative.

Either lap carries a tag.

These laps' ranges don't overlap on the requested grid — nothing to compare.

The two laps share no distance range at all.

Lap ‹id› (lap ‹n›) has no per-sample distance_m, so it can't be placed on a shared grid …

A session uploaded before per-sample distance existed.

Signing in

Your session ended — sign in again.

Web: a request was refused because the sign-in expired or is no longer valid; you are on the sign-in page and nothing was lost.

Your session has expired. Sign in again.

The same condition, as the API states it.

Invalid email or password

Sign-in refused. The message is the same whether the address exists or not.

Email already registered

Sign-up with an address that has an account.

Password must be at least 8 characters

Sign-up.

Rate limiter unavailable; try again shortly

A service the API depends on was briefly unreachable; every request is refused for a few seconds rather than let through unchecked.

Uploads are paused for maintenance; try again shortly

Uploads switched off for a maintenance window.

Teams and invites

Drivers see only their own sessions unless this is on; staff always see the whole team.

Under the visibility switch on the Team page.

Generates a shareable link (72h expiry, single-use) — send it however you'd normally reach the team (text, WhatsApp, in person). Optionally tie it to an email address so only that account can accept it. The link is shown once; you can revoke it below at any time.

Above the invite form.

Emailed / Not emailed

Beside a fresh email-bound invite: whether the email went out. A reason follows Not emailed when there is one.

This invite is tied to a specific email address.

On the accept page of an email-bound invite.

This invite was sent to a different email address

Accepting an email-bound invite from another account.

This invite has already been used. / This invite was revoked. / This invite expired on ‹date›.

The accept page; each names the person to ask for a new link.

This invite link doesn't exist.

The link is not an invite.

Only team admins/engineers can add cars

A coach or driver trying to add a car.

Only team admins can change team settings

A non-admin trying to change the visibility switch.

Devices and pairing

Devices paired via the DriverPeak desktop sync agent. Each can only upload sessions — revoking one takes effect on its very next upload attempt.

Top of the Devices page. In full, a paired device can upload sessions, list the cars it may upload against, and send a problem report with diagnostics; it can read or change nothing else.

No devices paired yet. Run the desktop sync agent and follow its pairing prompt.

Devices page, nothing paired.

Authorize desktop sync agent to upload sessions on your behalf?

The pairing page, with the device name and: This grants upload-only access — it can add new sessions to your team, but can't read, change, or delete anything else in your account.

This pairing link is missing a valid callback address, so it can't be completed safely here. Start pairing again from the desktop agent.

The pairing page opened from anything other than the agent's own local address.

This device was not authorized.

You pressed Deny.

This device has been revoked

An upload from a revoked device.

Desktop agent

Tray notifications and menu items of the desktop sync agent.

Paired! Right-click the tray icon to add a folder to watch.

After the first successful pairing.

Uploaded ‹file› (‹n› laps)

Each successful upload.

Failed to upload ‹file›: ‹reason›

An upload the server refused or that did not complete. The file is retried on the next scan; the reason is in the log.

Connected (click to pause) / Paused (click to resume)

The first menu item. Resuming rescans the watched folders for anything missed.

Diagnostics: on — sends crash reports, never telemetry files / Diagnostics: off

The menu item that toggles crash reporting; also printed when the agent starts.

No cars yet

Adding a folder when the account's team has no car; add one in the web app first.

Couldn't open the folder picker — opening the config file instead.

The folder dialog failed; the folder can be added by hand in config.json.

No response from the browser within 5 minutes — pairing cancelled.

Pairing page not approved in time; relaunch to try again.

Reporting a problem

Diagnostics include which browser platform you are on, the app version (‹v›), the page you are on (‹route›), the session you are viewing (‹id›), the last 50 lines of the desktop agent log it sent you here with. Nothing else is attached.

The web report dialog; the session and agent-log parts appear only when they apply.

Sent — we reply to ‹address›.

Report delivered. The report is saved; the email copy could not be sent right now, but support still sees it. is added when the inbox copy failed.

The desktop agent sent you here with its recent log lines attached (id ‹id›…). They are included only if you leave diagnostics on.

The Support page opened from the agent's tray item.

Diagnostics already used or expired; open the form from the agent again

The agent's log hand-off is single-use and lasts one hour.

Support is briefly unavailable; try again shortly

The report could not be stored; nothing was sent.

iPhone

Signed out — sign in again to continue.

The sign-in was no longer valid.

No connection — showing what's already on the phone. New sessions appear when signal does.

Banner on the logbook, sessions and team screens without signal.

Today's sessions download themselves over any signal and stay usable with none.

Footnote of the session list.

ON PHONE / CLOUD ONLY

Whether a session's laps are stored on the phone.

No connection — and this session isn't on the phone

Opening a cloud-only session without signal: Sessions marked ON PHONE in the list open without signal; this one was still cloud-only. It downloads itself when signal returns.

No connection — and nothing stored yet

The session list with no signal and no cache: This phone has no sessions saved and no signal to fetch them. They download themselves the next time the app opens with a connection.

No connection — the team page needs one. It loads itself when signal returns.

The Team screen without signal.

The logbook totals live on the server, and this phone has no signal to reach it. It loads itself when signal returns — or try again now.

The logbook without signal.

Saved — sends when signal returns

A report written without signal.

One report is waiting for signal and goes out on its own. / ‹n› reports are waiting for signal and go out on their own.

Reports queued on the phone.

Diagnostics include that you are on the phone app, the app version (‹v›), the screen you came from (‹screen›). Nothing else is attached.

The report screen's diagnostics sentence; the session is added when you came from one.

Pick two laps to compare

The session screen's compare button with fewer than two laps checked.

You're not on a team yet

An account with no team: paste an invite link or code, or create the team on the web.