Have you ever encountered a few stubborn tag reads that just won’t score? It’s a very rare problem, but it can be frustrating when it happens. We’ve identified a cause and have put in measures to help prevent stuck tags and proactively solve the issue when it happens. These improvements update the calculation logic around how FORCE or SKIP tags behave in the following scenarios:
- When the read is moved to another Race because the Athlete to which is was associated was moved
- Becomes disassociated from an Athlete because of the tag number being unassigned
In either of the above scenarios, the FORCE or SKIP reads will now always be reset to NEW so that they can be recalculated successfully. This will prevent possible scenarios where tag reads “go missing” or get “stuck” in the scoring engine.