Common Issues and Solutions

This article covers common issues users may face in RUFUS Race Manager (RRM) and provides practical solutions to address them.

1. Device Connection Problems

Problem: Device does not connect to RRM (either Cloud or Local).
- Solution: Verify that the device's IP address and port number are correct. Ensure that the device is assigned to the correct checkpoint and that there is an active internet connection (for Cloud devices). Check local network configurations for Local devices.
Problem: Cloud devices show "Offline" status.
- Solution: Ensure that the internet connection is stable. If the device remains offline, unbind and then rebind it to the event.

Problem: Timing data appears inconsistent across different views (e.g., web app vs. local Windows/Mac apps).
- Solution: Confirm that the internet connection is active to allow synchronization. Refresh or restart the local app if discrepancies persist. Data synchronization may experience minor delays, but typically resolves automatically.
Problem: Missing or incorrect passings for participants.
- Solution: If a participant's passing is missing or incorrect, add a manual passing from the Checkpoint-Race View or directly in the Edit Participant tab. Ensure the time is set appropriately if manually adding data in real-time.

Problem: Slow performance when viewing large events.
- Solution: Reduce the number of items displayed by using filters, or group data to reduce the visible load on the grid. Exporting data in smaller batches may also help.
Problem: Application freezes or fails to respond.
- Solution: Restart the application. If using the web app, try refreshing the page. Ensure the local machine meets the required specifications for optimal RRM performance.

Problem: Local changes do not appear in the cloud after reconnecting to the internet.
- Solution: Wait a few minutes for automatic synchronization. If issues continue, restart the RRM app. Remember that the system handles synchronization conflicts automatically when connecting back to the internet.

Problem: Participants not appearing in classifications or incorrect rankings.
- Solution: Ensure participants have a VALID passing for the final checkpoint. Check if the correct Race Order Segment is defined for accurate classification. Missing segments can prevent accurate classification calculations.

Problem: Unable to export results or reports.
- Solution: Ensure the grid data you wish to export is visible (i.e., filtered correctly). The export feature only captures what is visible. If there are errors with PDF/CSV exports, try reducing the dataset size.

Error: "Device Closed" or "Checkpoint Closed"
- Solution: Check the Device Control tab or Checkpoint Dashboard to confirm that the device or checkpoint is active. Reactivate as necessary.
Error: "Race Closed"
- Solution: This occurs if passings are received after the race has ended. Either adjust the race is processing passings, validate the passings if they are legitimate.

Always start with basic checks like internet connectivity and network settings.
If discrepancies persist, consider refreshing the app or restarting the software.
For issues with Cloud devices, unbinding and rebinding may help.
Use the Event Control View for a comprehensive overview of all incoming data, which can help pinpoint discrepancies or errors.

Last updated 7 months ago

1. Device Connection Problems

Problem: Device does not connect to RRM (either Cloud or Local).

Solution: Verify that the device's IP address and port number are correct. Ensure that the device is assigned to the correct checkpoint and that there is an active internet connection (for Cloud devices). Check local network configurations for Local devices.

Problem: Cloud devices show "Offline" status.

Solution: Ensure that the internet connection is stable. If the device remains offline, unbind and then rebind it to the event.

2. Timing Data Discrepancies

Problem: Timing data appears inconsistent across different views (e.g., web app vs. local Windows/Mac apps).

Solution: Confirm that the internet connection is active to allow synchronization. Refresh or restart the local app if discrepancies persist. Data synchronization may experience minor delays, but typically resolves automatically.

Problem: Missing or incorrect passings for participants.

Solution: If a participant's passing is missing or incorrect, add a manual passing from the Checkpoint-Race View or directly in the Edit Participant tab. Ensure the time is set appropriately if manually adding data in real-time.

3. Software Performance Issues

Problem: Slow performance when viewing large events.

Solution: Reduce the number of items displayed by using filters, or group data to reduce the visible load on the grid. Exporting data in smaller batches may also help.

Problem: Application freezes or fails to respond.

Solution: Restart the application. If using the web app, try refreshing the page. Ensure the local machine meets the required specifications for optimal RRM performance.

5. Classification and Results Issues

Problem: Participants not appearing in classifications or incorrect rankings.

Solution: Ensure participants have a VALID passing for the final checkpoint. Check if the correct Race Order Segment is defined for accurate classification. Missing segments can prevent accurate classification calculations.

7. Common Errors and Messages

Error: "Device Closed" or "Checkpoint Closed"

Solution: Check the Device Control tab or Checkpoint Dashboard to confirm that the device or checkpoint is active. Reactivate as necessary.

Error: "Race Closed"

Solution: This occurs if passings are received after the race has ended. Either adjust the race is processing passings, validate the passings if they are legitimate.

Tips for Troubleshooting

Always start with basic checks like internet connectivity and network settings.

If discrepancies persist, consider refreshing the app or restarting the software.

For issues with Cloud devices, unbinding and rebinding may help.

Use the Event Control View for a comprehensive overview of all incoming data, which can help pinpoint discrepancies or errors.

If you need further assistance, please contact RUFUS Support or refer to the official help documentation at or write to