“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.