Review runs
Race Control matches the event and sessions when the bridge reads Orbits. Schedules exported by Race Control match by their generated run codes, dates and timing modes, even when staff change the class descriptions in Orbits.
- Select the bridge's name in the Bridges list.
- Open the desktop app and select Start Bridge.
- Check Current Orbits Event and Current Race Control Event. The display updates automatically.
- Read Event Routing and its reason if the destination is waiting or does not match.
Run Mappings starts with Current Orbits Event. Choose All Orbits Events or a retained source in the Orbits Event filter to review earlier timing. Use Run State to find running, stopped or paused runs, or select Needs Attention for missing session matches, withheld rows, paused timing and old running observations. Search Runs finds run, session and event names or a run ID. Filters stay in place when status refreshes.
The list keeps the run name, session, state, withheld count and last observation together. Last Seen Running means the running observation is more than 90 seconds old or has no valid observation time. A current Bridge connection does not establish that each run's observations are current. The Running filter includes these retained observations. Read the state to distinguish Running from Last Seen Running.
Open a run's Actions menu and select View Details for counts, source and destination events, application times and timing messages. Use Timing Alerts from those details to review the event's timing issues.
Resolve a run match
Open the run's Actions menu and select Configure when its match needs staff review. The Configure Run dialog shows the source and destination events. Check its Orbits event and Race Control event, select the local session, then select Save Run Mapping. An approved source keeps its destination event. If the event match needs review, select the matching Race Control event first. The bridge checks the source event and session kind before it applies timing.
Scheduled sessions use the calendar day in your organization's timezone. If several events match, or several events are running, automatic timing waits for review. A running event that does not match also needs review.
If Orbits recreates its runs, the Bridge can restore a session match after checking the complete event. Each replacement must uniquely match the same exported session. Manual timing files and paused sessions keep their settings. If replacement runs stay unmapped, check Diagnostics for a Bridge update.
Create the event schedule first if the session list is empty. Orbits can time warmups in practice or qualifying mode. Warmup sessions and older Practice sessions coded WU1, WU2, and so on accept either mode automatically when the run matches.
Check traffic
On the selected Bridge, use Traffic to review requests and transfers to and from Orbits. The list shows the latest rate; the graphs show the selected period. Old measurements are marked Stale, and missing measurements remain gaps. Read Bridge traffic explains rates, minute summaries, coverage and retention.
Enable automatic timing
Review the source and destination shown for the current event. Select Enable Automatic Timing to allow timing for matched events and sessions. The bridge can wait for the next event with automatic timing enabled. Timing that needs an event or session match waits for review. Use Observe Only to stop automatic application while the bridge continues to collect timing.
The bridge shows the last application time and any blocked reason. A manual timing file keeps authority over automatic timing.
To return a session to automatic timing, open Event › Schedule, select View, and select Remove Manual Import. Confirm the removal. Race Control uses the latest valid automatic timing when available. If the source is unavailable, the session waits for it. The original import stays in the history.
Remove Timing clears timing and pauses automatic updates. Use Resume Automatic when you want updates to continue. The bridge does not replace a manual file on its own.
With automatic timing enabled, the bridge also updates session state. A running Orbits session becomes In Progress. Verified finish evidence makes it Completed. Future sessions stay Scheduled, and cancelled sessions stay cancelled. Preloaded race rosters and DNS rows do not become results before the race starts.
A manual timing file still controls results while the bridge updates state. Completed sessions still need staff result approval.
Race Control keeps grid generation and publication explicit. The bridge does not regenerate grids or finalize results. Use the event's normal review and publication workflow.
Catch up missed sessions
The Bridge reads saved results from Orbits after a missed session. It checks every day of the current event after startup, reconnection or enabling automatic timing. Orbits must still hold those results. Live timing takes priority while earlier sessions catch up.
During normal collection, active timing updates about every five seconds. The three most recent stopped runs and the next two scheduled runs get full timing checks about once a minute. Other runs in this event get full checks about every five minutes, including staff corrections. The Bridge checks for starts more often and reads complete timing when a run starts or stops. Busy reads or connection failures can delay these checks.
Open the named Bridge and read Event Catch-Up. It shows how many mapped sessions the Bridge has checked for the current scan. Checks include sessions that have not started.
Automatic Timing Applied counts sessions with usable Bridge timing. Manual Timing Retained counts sessions whose manual or approved timing keeps authority. Paused Sessions stay paused. Use Sessions Needing Review and the Run Mappings list to find mapping or identity issues. Partially applied timing can still need review.
Empty practice and qualifying rosters do not count as timing needing review. Open Event › Schedule › Timing Alerts to review unresolved timing rows. The Bridge uses current event registrations, including practice-only riders and separate bikes. Old transponder assignments remain supporting history.
One rider can move a transponder between bikes. Race Control uses the current run's registration to identify the bike; a Friday practice bike does not block a Saturday race result. Different riders claiming the same device in the same run still need review. Warmups use the audience configured for that run.
If a known rider has no practice registration, an Operator or Admin can accept their practice timing with a reason. This does not register them for races or allow qualifying runs. See Resolve timing alerts.
An organization Admin can select Rescan Current Event to request a fresh check, including results that have not changed. The request keeps the current timing mode. In Observe Only, it collects observations without applying them. If the Bridge is offline, the request waits for it to connect. A rescan waits while the Bridge is stopped.
If scan progress is unavailable, check the desktop app's Diagnostics for an update. Wait for the full event check to finish before assessing missing sessions. Catch-up preserves manual imports, paused timing, published grids and staff approvals.
Sync selected sessions
An organization Admin can ask a Bridge to read timing for a past event or completed sessions in its current event. Use this for a corrected result without restarting the whole event check. The Bridge keeps following the current live event while it checks the requested sessions.
- Open the event's Schedule.
- Select Sync from Bridge.
- Choose the Bridge and its Orbits Event. Check both event names and dates.
- Review Session Matches. Select a local session when a match needs review.
- Select Sync Selected Sessions.
Race Control suggests a source when its name, season and session configuration match. The source dates and run count help distinguish events with similar names. Runs outside the event dates stay Excluded. Leave a run Not Matched to omit it from this request. Each local session can match only one native run in a request. For the current event, leave scheduled and running sessions Not Matched; only completed sessions can be requested, from the Bridge's current Orbits event.
The page shows sessions checked, automatic timing applied, sessions enriched, results enriched, manual timing retained, paused sessions and timing that needs review. Reads Completed means the selected sessions were checked; it does not mean every result has usable times. A session can apply useful timing and still need review for some riders. Open Timing Alerts to resolve those rows. The Bridge uses the selected event's registration evidence when matching riders.
Session Details labels live review counts with "Current timing" while the same retained observation still owns that session. A registration correction can clear these counts without another sync. "At last check" labels saved counts when the original observation is no longer current or a manual file controls the results. The saved request history stays in place.
A request can wait while the Bridge is offline. Install the latest Bridge version and let it report a complete Orbits catalogue before selecting a source. After an interruption, it resumes the sessions it has not checked. Live timing takes priority, so a historical sync can take several minutes.
Select Cancel Sync to stop further reads. Timing already collected stays available. Use Repeat Sync for another fresh check after a request finishes. A changed source, date or session mapping can put the request in Needs Review. Review the source and matches before requesting another sync.
Manual timing files and approved results keep authority over automatic timing. Retained Bridge results can fill missing lap counts and times when the result matches uniquely in the same session. Supplied times, finishing order, statuses, motorcycles, exclusions and staff decisions stay in place. Ambiguous matches, conflicting supplied times and contradictory DNS results need review. The original file and Bridge observation remain available as their separate sources.
Previously captured Bridge timing can supply missing fields without another sync. Observe Only and paused timing still apply.
Use Manage Timing to remove a manual import only when you want automatic timing to take over the classification as well. The sync keeps published grids and the Bridge's current live event unchanged.
Bridge sync status updates automatically. Your matching choices and open details stay in place. A failed status read keeps the previous progress and retries automatically; you can still select a source or issue an available sync command while a status read is pending.