> ## Documentation Index
> Fetch the complete documentation index at: https://docs.time2.bike/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Common race-day timing problems and fixes.

## "Session not found" on a volunteer's phone

Their token was revoked or expired. Issue a new one from **Tokens** and have them rescan.

## Clock indicator shows ±500 ms or more

Bad network conditions. The rolling median will tighten as more samples come in. If it stays bad:

* Move the device to a stronger Wi-Fi spot.
* Make sure your device clock isn't dramatically wrong (occasional issue on phones with disabled auto-time).
* Pull-to-refresh the page to re-init the worker.

## Two devices recorded the same rider

The row shows a **duplicate** badge. Open the row menu, choose **Resolve**, and pick which finish to keep. The other one is hidden but still recoverable from the row history.

## Finish arrived before start

The row shows **awaiting start**. Hit **Race start** for that race — elapsed times back-fill automatically.

## Finishes aren't draining (queued count stuck)

* Check the sync indicator. If it's red, you have no network.
* If it's yellow but not decrementing, pull-to-refresh.
* Worst case, click **Export log** in the footer and send the file to the race director, who can replay it back into the session.

## RFID watcher stopped reading the file

* The browser tab was put in the background; some OSes pause file watchers.
* Re-pick the file from the RFID panel to resume.
* If you swapped USB drives, the browser lost the file handle — re-pick.

## Volunteer's screen went to sleep

Some phones throttle background tabs when the screen sleeps. Set the device to **never sleep** while plugged in. The operator screen tries to keep the screen awake on its own, but device settings can override that.

## I finalized too early

Manager-only **Unfinalize** in the session menu re-opens the session. Make corrections, finalize again, publish (or republish).

## A finish is on the wrong race

Long-press → **Delete**, switch race tabs, re-record. The original delete + re-record is preserved in the event log.

## Where's the audit log?

Every action — including who issued which token and when — is recorded server-side. Contact support if you need a copy.