Skip to main content
The one rule worth remembering: nothing you can press loses data. Every entry, edit, and deletion is recorded, so any mess can be unpicked afterwards. When in doubt, keep timing and sort it out later.
!!-IMAGE-NEEDED-!! — The sync indicator in each of its three states: green, yellow with a count, and red.

​
A volunteer’s device says “session not found”

Their link expired or was revoked. Issue a new one from More actions → Operator tokens and have them scan it. Everything they already recorded is safe.

​
Nobody pressed Start

Keep recording finishes — they’ll show as awaiting start. Then use Set the start time under the start buttons and type the time the race actually went. Every elapsed time fills itself in from that moment. Type the real start time rather than pressing START RACE now: a gun stamped after those riders crossed the line can’t produce a time for them. For a wave nobody released, the wave board has the same control — see Waves.

​
Finishes went into the wrong race

Switch to the correct race tab first, so nothing else lands wrong. Then delete the misplaced finishes and re-record them under the right tab.

​
Two phones recorded the same rider

That rider’s row shows a duplicate flag with both times. Open it, pick the one to keep, delete the other. Neither is thrown away before you choose.

​
The queued count isn’t going down

  • If the dot is red, there’s no signal. That’s not a fault — keep timing.
  • If it’s yellow and stuck, pull down to refresh.
  • If the phone is in real trouble, use Export log at the bottom of the screen and send the file to your race director, who can load it back in.

​
The clock indicator shows a big number

The ± milliseconds figure is how sure that phone is of its own clock.
  • It usually settles within a minute on its own.
  • Move to better signal if it doesn’t.
  • Check the phone’s clock is set to update automatically — a phone with the wrong time set manually is the usual culprit.
  • Pull down to refresh.
Outside of two-lane head-to-head racing, a few hundred milliseconds doesn’t change anyone’s result.

​
A timing phone died

Anything it had uploaded is safe and visible from any other device. Anything it hadn’t is on that phone — charge it and let it connect. Prevent it: battery pack per phone, and check for a green dot before anyone packs up.

​
The RFID watcher stopped reading

  • The tab went to the background and the computer paused it. Bring it back to the front.
  • Re-pick the file to start it again.
  • If you swapped drives, the browser lost track of the file — re-pick it.

​
A volunteer’s screen keeps sleeping

Set the phone to never sleep while plugged in. The timing screen tries to keep itself awake, but the phone’s own settings win.

​
I finalized too early

Unlock the timer, correct it, finalize again, and republish if you’d already published.

​
A rider says their time is wrong

Look at the row. You can see what was originally recorded, what’s been changed since, and who changed it — so you can answer the question rather than guess. Fix it with Set manual time if they’re right, then finalize and publish again.

​
Everything is broken and the race is starting

Time on paper. Record finish times by hand, then enter them afterwards with Set manual time on each rider. Results publish exactly the same way.

​
Something else

Screenshot it and contact support. The full history is kept on Time2Bike’s side, not just on the device — so nothing is lost even if the one in your hand is unusable.