Troubleshooting | Outlap Docs

Find your symptom, then work down the list. If you’re still stuck, contact support with the details listed at the end.

API errors

`401 invalid api key` or `missing bearer token`

The header must be exactly Authorization: Bearer <key>. Check there is no extra whitespace or newline from copy and paste.
The key may have been revoked. Create a new one in Settings → API keys.
Keys aren’t recoverable. If you’ve lost it, mint another.

`403 event does not belong to api key's club`

The key belongs to a different club than the event. Use a key from the club that owns the event, or check you copied the right event ID.

`403 insufficient scope`

The response lists required_scope and granted_scopes. Create a key that has timing:write.

`404 not found` on a GET

Public reads work only for events with public visibility. A private event returns 404 to unauthenticated reads, and so does a wrong ID.

`429 rate limit exceeded`

Wait Retry-After seconds, then batch more. See Rate limits.

`400 invalid lap_time_ms`

Lap times are milliseconds as a number, greater than 0 and no more than 24 hours. "1:32.345" as a string isn’t accepted by Ingest laps. Convert it to 92345.

I posted a lap twice and see two

POST /laps doesn’t de-duplicate. Mark the extra lap invalid in Race Control. For continuous feeds, use /stream, which does.

Timing bridge

`ECONNREFUSED` or “connecting …” forever

The bridge can’t reach your timing system.

Is the RMonitor output enabled in the timing software? See Orbits, Trackside, AxWare.
Is the port right? The default is 50000.
Running on another machine? Use the timing PC’s IP for --host, and check the firewall allows the port.

The bridge retries on its own, backing off from 1 to 30 seconds, so once the cause is fixed it reconnects.

Connected, but Race Control shows the feed as stale

A feed is stale when no packet or heartbeat has arrived for a while. Check the bridge window is still running and still prints +N lap(s) lines during a session.
Check the PC’s internet connection. The bridge queues failed uploads (up to 20,000 lines) and retries, then recovers by itself.
A queue of more than 5,000 lines is reported as stale until it drains.

Laps appear, but not against drivers

The transponder or car number isn’t on the Paddock roster, or doesn’t match exactly. Add or correct it, then assign the unmatched laps under Fixes. See Transponders & numbers.

`recognised` is 0 or very low

The wrong output is enabled, so the lines aren’t RMonitor. Check the output type in your timing software and the record list.

Rehearse without hardware

node bridge.mjs --event <eventId> --key <apiKey> --file sample-rmonitor.txt --replay

If laps from the sample appear, the connection to Outlap is fine and the problem is on the timing-system side.

Logger import

No laps were found

AiM: re-export CSV from Race Studio 3 with the GPS channels included.
Garmin: .fit files aren’t read. Export GPX from Garmin Connect.
A file with no GPS and no lap markers can’t be timed.

Fewer laps than expected

Out-laps, in-laps and pit stops are dropped by design: laps under 15 s, over 15 min, or more than 1.6 times slower than your median. The import summary says how many were skipped.

Lap times differ from my logger

Outlap re-times from GPS against the circuit’s start/finish line. See GPS lap timing.

Sectors don’t match the circuit

If no start/finish was found in the file or the circuit database, a line across your fastest straight is used. Lap times are unaffected, but sector positions differ.

RaceBox

The device doesn’t appear when pairing

Use Chrome or Edge. Safari on iPhone and iPad doesn’t support Web Bluetooth.
The RaceBox must be on and not connected to another app.
The picker only lists devices whose name starts with “RaceBox”.

Poor accuracy

Wait for a 3D fix with plenty of satellites before driving. Tunnels and tree cover degrade the fix.

Calendars and embeds

My calendar app doesn’t show new events

Subscribed feeds refresh on the calendar app’s schedule, often every few hours. Outlap caches the feed for 10 minutes.

The embed is blank

Your site may block iframes. Allow frame-src https://app.outlap.xyz in your Content-Security-Policy.
Event listings show only published, public events.

What to send support

Include: the event ID, roughly when it happened (with timezone), the exact error text, the HTTP status, and for bridge issues the last 20 lines of its output. Never send your API key. Support will never ask for it.