Resolving issues on the day

Audience: Timing operators dealing with problems during the event.

Recipes for the common things that go wrong during a live event and how to fix them in Manager.

Status: Stub — not yet written.

What this page will cover

Each recipe will be a short "symptom → diagnosis → fix" block.

[ ] Competitor shows as "In Forest" hours after finishing
[ ] Competitor has a finish punch but no start
[ ] Competitor's SI card reads but they're not in the competitor list
[ ] Competitor ran the wrong course
[ ] Radio control stopped reporting
[ ] meshO Prime disconnected mid-event
[ ] A punch is visibly missing from a competitor's card
[ ] Same SI card used by two competitors
[ ] Start time clearly wrong (e.g. off by an hour)
[ ] Results show a DNF that should be OK (and vice versa)
[ ] Network / TCP forwarding dropped
[ ] Late entry needs to be added after the event has started
[ ] Setting a whole class to DNS
[ ] Entering times manually when hardware fails (keyboard time entry)
[ ] Editing or correcting individual punches on a competitor's record
[ ] Adjusting for SI unit clock drift (a control's clock was off)
[ ] Approving or disqualifying a competitor (operator override of auto-status)
[ ] Voiding a leg across the class (a control was vandalised or malfunctioned)
[ ] Start interruption — event paused and resumed, adjusting affected competitors' times
[ ] Swapping in a replacement control unit (a box failed mid-event)
[ ] Finding and marking all no-shows as DNS in bulk