Automatic registration checks and alerts

A registration alertA saved event notice for a missing transponder, number or identity review, registration conflict, failed check, or starter change that needs review. keeps each issue available for review.

Open Event › Entries › Registration Alerts to see the last attempt, last successful capture, next check, and any errors. Live-linked events check every minute during their event dates, including Friday practice, in the club's time zone. An Operator can pause Automatic Registration Checks or select Check Now, including before the event starts. Saved snapshots stay fixed.

This page updates automatically every five seconds. Updates wait while you use menus or dialogs and preserve your selection. Display updates and the club's automatic MotorsportReg checks run separately. Select Check Now to fetch registrations immediately.

If another update briefly prevents an automatic check from starting, Race Control retries automatically. If Check Now reports that checks are busy, wait briefly and try again. The last successful registrations remain available.

The Checking Again status means the previous check failed and another check has started. The page shows when that check started and its elapsed time at the last refresh. The previous failure does not mean the new check failed. The last successful registrations remain available while it runs.

Status Unavailable means the page could not refresh its display. Times and alerts are from the last successful refresh; they do not confirm a check is still running. Race Control retries automatically and restores current status when the read succeeds.

Once required product mappings are reviewed and saved, live checks apply safe starter and qualifying changes automatically. This includes registrations added or removed and changes to eligible statuses. Saved product mappings and individual eligibility decisions still apply.

Changes that need identity, product, or vehicle review stay in Registration Alerts. They hold the affected races while other safe changes continue. Correct the named issue in Entries or Registration Review. Select Check Now to check the corrected live registrations immediately. Review and regenerate affected grids separately. Saved grids never update automatically.

For a Race Control schedule, save the product review before starter updates can apply. Select Update Race Starters to use the saved registrations immediately. Saved snapshots require this explicit update.

An organization Admin selects eligible registration statuses in MotorsportReg Defaults. Confirmed and Checked In are the defaults. Review that policy before changing it.

The event header shows Registration Alerts and its count for unresolved actionable alerts that still need acknowledgement. On a wide desktop screen, select it. On a narrow desktop screen, open the Alerts menu and select Registration Alerts. The menu lists each alert type with its count.

On a phone, the Open Navigation button shows the combined alert count. Open it and select Registration Alerts in the navigation drawer. The drawer lists each alert type with its count.

Acknowledged alerts remain available in history. Open a row's Alert Actions menu and select View Details to see the riders' names and numbers, affected assignments, first and last observations, and history. Repeated claims on one conflicting transponder share one alert.

Missing transponders also appear here. One alert groups a rider's affected products and runs. Open its details and select Open Orbits to review them. Practice uses the same device fallback as the Orbits download, so a blank source field with a usable fallback does not cause a missing-transponder alert. For current and future events, correct the registration source, then refresh the event data.

After the event's full end date in the club's time zone, a missing transponder has the Source Gap state. It describes incomplete saved registration data for an ended event. It is not a current timing blocker. It does not increase the event warning count or system monitor warning counts. The default Unresolved view still includes it; select Source Gaps to inspect these cases, including resolved ones.

Details retain the affected assignments, prior acknowledgements, and history. Source gaps have no Acknowledge action. Timing observations do not fill the registration source or assign a device to a rider. Number, identity, application, and check failures keep their usual review rules after event dates.

An unconfirmed event-number difference creates an alert for that rider. Select Number Reconciliation in the alert to compare the numbers and confirm the choice. Confirmation resolves the alert even when the source numbers differ.

Rider identity cases also appear as alerts, including proposed name corrections. Select Open Entries, then the review button to resolve or dismiss the case. These alerts use the same cases as the Entries review panel.

These three alert types also use saved event data outside event dates. They resolve when you correct the saved data or review decision. After the event end date, a missing-transponder case changes only its display and warning count. This does not resolve or acknowledge the case.

A shared-transponder alert means the source supplies a number for different riders. It does not mean the transponder number is missing. Each affected assignment shows its rider, number, product, and physical run when known. Two riders can share a transponder in separate reviewed runs.

A reviewed practice product can have no scheduled run. In that case, it is supporting information and does not block known race or qualifying assignments.

Claims in the same run need review. An unknown run also needs review. Correct the source or review the product destinations, then select Check Now. For a saved snapshot, use Update Race Starters after the correction.

Distinct MotorsportReg profiles stay separate when riders share an account, motorcycle, or transponder.

Duplicate-number alerts compare riders registered at this event and their current event numbers. A rider's old club number does not cause an event conflict. If two riders share a number, correct it in MotorsportReg. The next complete successful check resolves the alert when their event numbers differ. A rider who is absent from this event does not cause a duplicate-number alert.

Acknowledge marks the current alert details as reviewed. It keeps the alert open until a complete check or saved-data review observes the correction. Changed alert details need acknowledgement again. Use the Show selector to find acknowledged or resolved alerts. A failed check keeps the last good registrations and existing alerts available. Informational missing-number rows do not increase the warning count.

Repeated reads of unchanged saved data do not reopen a case or change its review history. Synchronization does not erase saved reviews. Changed observations need review again; a failed source projection preserves existing cases.