# Common Issues and Solutions

Even with a well-designed system like the RUFUS Timing App, you may encounter issues during setup or usage. Here are some common problems and their possible solutions to help you troubleshoot effectively.

## 1. **Unable to Connect the RFID Sled to the Timing App**

* **Issue**: The RFID sled is not connecting to the Timing App via Bluetooth.
* **Solution**:
  * Ensure that Bluetooth is enabled on both your mobile device and the RFID sled.
  * Confirm that the sled is in pairing mode.
  * Restart the Timing App and try reconnecting.
  * Check if the sled’s battery is charged and if it’s listed as a paired device in your phone’s Bluetooth settings.

## 2. **Passings Are Not Being Sent to the Cloud**

* **Issue**: Passings are not syncing to the RUFUS Cloud.
* **Solution**:
  * Verify that the mobile device is connected to the internet.
  * Check the Cloud account to ensure that the Timing App is properly bound as a Cloud Device.
  * If you see grey passings in the session list, try reconnecting to the internet and waiting a few moments for them to sync.
  * Unbind the device from the cloud and bind it again.

## 3. **Location Data Not Recorded for Passings**

* **Issue**: GPS location is not being added to passings.
* **Solution**:
  * Make sure the GPS location feature is enabled in the app settings.
  * Allow location permissions for the app in your device settings.
  * If the system did not request location access when the session started, exit and re-enter the session to trigger localization.

## 4. **RFID Tags Are Not Being Read by the Sled**

* **Issue**: The RFID sled is not reading participant tags during the race.
* **Solution**:
  * Check if the sled is correctly connected to the app and the battery level is sufficient.
  * Verify that the correct tag type (e.g., RUFUS Tags, RUFUS FREE, or Custom Format) is selected in the **RFID Zapper** settings.
  * Ensure that the RFID sled is within the appropriate range of the RFID tags.

## 5. **Timing Session Not Saving Properly**

* **Issue**: Timing session data is not being saved or appears lost.
* **Solution**:
  * Ensure the **Autosave** feature is enabled in the app settings to save session data automatically at regular intervals.
  * Save the session manually before closing the app.
  * If the app crashes, check the archive to see if an autosaved version of the session is available.

By addressing these common issues, you can ensure smoother operations during your events and minimize disruptions. If problems persist, consult the RUFUS support team for further assistance.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.runonrufus.com/rufus-timing-app/troubleshooting-and-faqs/common-issues-and-solutions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.