# Reprocess Passings

Sometimes passings (recorded times) need a second look. Maybe a passing isn’t assigned to the correct participant, or the system flagged it as invalid due to a missing registration. The **Reprocess Passings** feature lets you correct these issues quickly and efficiently. Whether you have orphan passings or invalid checkpoint times, you can run the logic again to make sure every passing is assigned correctly.

## What Is “Reprocess Passings”?

Reprocessing a passing means telling RUFUS Race Manager to re-run the timing logic on one or more selected passings. This is especially useful in scenarios such as:

* **Orphan Passings**: Passings that aren’t linked to any participant (e.g., because the participant was added after the passing was recorded).
* **Closed Checkpoints or Races**: If a checkpoint or race was incorrectly marked as closed, passings recorded during that time may have been flagged as invalid.
* **Invalid Times**: When a passing doesn’t match the expected time sequence or was attributed to the wrong race or checkpoint.

By reprocessing, you give the system a chance to pick up any new information (like a newly created participant) and correctly assign or validate these passings.

## How to Reprocess Passings

1. **Open any Passings Grid**
   * Navigate to a passings list in RUFUS Race Manager where you can see all recorded times.
2. **Select the Passings**
   * Highlight the passings you want to reprocess. You can choose one or multiple rows at once.
3. **Click the Action Icon**

   * Look for the “Actions” icon (typically at the top or within each row). Click it to reveal a menu of possible actions.

   <figure><img src="/files/Q1Z5ifwI7nWRMTvxViLg" alt=""><figcaption><p>Reprocess passings</p></figcaption></figure>
4. **Choose “Reprocess Passing”**
   * From the expanded menu, click **Reprocess Passing**. This triggers the system to re-run the assignment and validation logic for those selected entries.
5. **Review the Results**
   * RUFUS Race Manager will update the passings with the corrected information. If any passing remains invalid or orphaned, check that the participant or checkpoint data is correct, then repeat the process if needed.

## Example Scenario: Orphan Passings

Suppose you have a list of orphan passings—times recorded by chip numbers or BIBs that don’t yet correspond to any known participant. If you **add the missing participant** (or correct their information) and then **reprocess** the passings, RUFUS Race Manager will now be able to associate those previously orphaned passings with the correct competitor.

## Tips & Best Practices

* **Double-Check Participant Data**: Ensure participant numbers or chip codes are accurate before reprocessing, so the system can match passings correctly.
* **Pay Attention to the Timing Gaps**: If a passing still appears invalid after reprocessing, verify the checkpoint’s open/close times and the participant’s possible start/finish windows.
* **Batch Processing**: You can select multiple passings at once, which is especially useful after a bulk data import or when fixing large-scale errors.

## Conclusion

**Reprocess Passings** empowers you to fix timing errors on the fly—whether you’re dealing with newly added participants, incorrect checkpoints, or any other anomalies. By selecting the problematic passings and clicking “Reprocess Passing,” you can ensure all data is accurately assigned and up to date. This feature helps keep your event’s timing data clean, streamlined, and reflective of what actually happened on race day.


---

# 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-race-manager/collecting-and-managing-timing-data/reprocess-passings.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.