Resolve timing alerts
Select View beside a session to inspect saved timing and identity decisions. Viewers can read these results. An Operator or Admin can recheck the original file, save timing decisions, or remove timing.
When Race Control finds unresolved timing disagreements, the event header shows Timing Alerts and its count. Unavailable means the check failed.
On a wide desktop screen, select it. On a narrow desktop screen, open the Alerts menu and select Timing Alerts. On a phone, the Open Navigation button shows the combined alert count. Open it and select Timing Alerts in the navigation drawer. Both lists show each alert type with its count.
You can also go to Event › Schedule › Timing Alerts to see each affected session with its date and time, competitor, source class and result. A race result shows its position or status, such as P3, DNF or DNS. A practice or qualifying result shows its best lap. Automatic updates keep the list current while you work. These alerts are separate from Registration Alerts.
An alert can mean an unknown rider, conflicting names or numbers, or a known rider whose bike or registration does not fit that session. Each row explains the issue and its effect. Held rows supply no qualifying time or participation credit. Registration corrections update the timing view without another CSV upload. Qualifying changes still need grid review and explicit regeneration.
An unresolved race alert holds the public results for the whole race, even if it affects one rider or class. Riders see Results under review on the race page. Published grids and Live Timing remain available. Correct the source or registration, assign the claim to the right rider, or exclude an incorrect row with a reason. When the last alert for the race clears, the usual publication rules apply automatically.
Bridge timing uses the event's current MotorsportReg assignments. An older saved transponder association does not override an agreeing current rental assignment. Practice riders can match their practice registration without a race entry. Separate registered bikes can keep separate practice timing rows for one rider. Empty practice and qualifying rows raise no timing alert and do not block another row that has a best lap.
Choose Review in the row's action menu. Check the source result and the reason its rider attribution or qualifying time needs review. Open Timing Details for supplied laps and times, the transponder, import time and full matching details. Compare the source row with the candidate riders and their classes.
When riders share a name and number, the rider choices also show their event classes. No current event classes identifies a rider without classes in this event. Compare these details before selecting a rider.
Use Find Another Rider when the right rider is missing. Select a rider, or exclude the row from local timing use, enter a Reason, and select Save Timing Decision. Viewers can inspect the matching details; an Operator or Admin saves decisions.
If a corrected Orbits race result names an eligible rider who used the wrong transponder, select that rider under Timing Decision. Enter a Reason and select Save Timing Decision. This assigns the retained result, laps and times to that rider in this race. The registration and saved transponder records stay unchanged. Race Control keeps real eligibility and shared-device conflicts for review.
A saved decision does not always clear the alert. If the claim still needs review, Race Control says the decision was saved and its timing remains held, then shows the current reason. A rider choice cannot identify which of two motorcycles set a lap in the same run. Correct an incorrect product mapping or source assignment in Registration Review, or capture corrected registration. Do not choose a motorcycle to guess which bike set that lap.
For a known rider with a race eligibility mismatch, select Review Registration. Check the product's race, class and motorcycle in Registration Review. A timing assignment to the same rider does not grant eligibility or resolve that mismatch. Select Correct Rider Identity only when the source result belongs to a different rider. Use Exclude This Result only when you intend to withhold the source result from local use.
For Bridge timing with a known rider missing practice registration, review the source timing and candidate rider. Choose Accept Practice Timing, select the Practice Rider, enter a Reason, and select Save Timing Decision. Acceptance applies to that practice timing only. It adds no registration or qualifying or race permission. Choose Reject Practice Timing to exclude the row instead. Viewers can inspect the alert but cannot accept or reject it.
For an unexpected qualifying run, choose Allow Qualifying Run or Reject Qualifying Run. To allow it, select the registered Motorcycle that was used, check the listed Affected Race Entries, and give a Reason. A rider with more than one bike requires an explicit bike choice; the rider's name and lap time do not identify the motorcycle. The run joins that bike's previously permitted runs for the listed races. Other bikes keep their qualifying scope. An explicit manual Time or Missing override remains in force, and the race class must already accept this run.
When you reject the run, its time remains excluded. Both choices keep the source CSV and an audit record. Review and regenerate affected grids separately.
The decision retains the original CSV or Bridge observation and can survive a corrected time or re-import of the same claim. A registration refresh that only changes row order keeps the decision. Changes to the rider, motorcycle, number, inclusion or qualifying-run evidence can reopen review. If those records change while you review it, your draft stays open so you can compare the current facts before saving again.
A reviewed motorcycle in a separate physical run does not compete with an exact current-run motorcycle using the same transponder. A warmup that copies a qualifying audience keeps that run's motorcycle and transponder context too. Unknown run claims and two motorcycles registered for the same run still need review.
An older warmup decision needs one new review because its audit did not name the copied qualifying run. New warmup decisions retain that exact source. They survive unchanged updates; a change to the copied source reopens review, even when both runs have the same riders and motorcycles.
Correct unidentified riders in Orbits. Choose Open Schedule, then select Manage Timing in that session's action menu. Upload the corrected results against the same session with Approved Results selected. For a named rider who is missing from the event, check their registration too. A corrected import clears rows that now match; rejected imports leave the alerts in place. You do not need to dismiss them.
Keep the original results scope when correcting it. A class-only update does not clear unknown rows from a complete-session export.
Resolve a timing identity conflict
Open the session's View action. Under Review timing identity, compare the CSV number, name, and transponder with the listed registered riders. Use Find another rider to search by name or number when the suggestions do not include the right person. Select who made the crossings, enter a Reason, then select Save Timing Decision. If you cannot assign them, select Exclude these crossings and explain why.
Until you decide, these crossings supply no qualifying lap or event number. Grids that require this session show Needs review and cannot be generated or published. Grids that use other sessions can continue.
The decision applies to the same claim in this session and survives a re-upload. It rebuilds timing from the retained original CSV and leaves registration names and transponder records intact. Check the affected grids and publish any revised grids through the normal review flow.
For an older import, select Recheck Original File to check its retained CSV again. If that import had already assigned someone the wrong event number, open Entries and review the number difference there; choose the registration number for that rider. The timing decision does not remove a previously stored number choice.
A disputed race crossing can change the finish order or whether someone started. Resolve the timing conflict to clear its hold on public results. Qualifying keeps the uncontested laps while you review the remaining crossings.