Edge Cases & Limitations

Despite all the safety checks and recovery mechanisms in place, TimingDash depends on the availability and stability of RIS Timing, especially of the web live timing feed. Below are some known edge cases and how the software behaves in each situation.

RIS Offline for a Few Minutes

If RIS goes offline for a short period (e.g., a few minutes), and some laps are not received:

• Most of the system will continue working with minimal disruption.
• Lap history for the missing laps will be incomplete.
• Fuel strategy calculations rely on the current lap and the fuel stint start lap.
  These will automatically re-sync as soon as RIS resumes and new laps are received.

⚠️ Edge case:
If an IN lap occurs while RIS is offline, the system might miss the stint split, resulting in two stints being incorrectly merged on the Stints page.

Lap Penalties or Lap Removals

If laps are removed by race control (e.g., as a penalty):

• TimingDash is not designed to handle “laps going backward”.
• Example: if your car is at lap 190 and receives a 2-lap penalty, you won’t see any new laps appear until lap 191 is reached again.

Impact on Fuel Strategy

• Fuel calculations will not adapt automatically.
• Recommended workaround:
  Subtract X laps × Green Flag Consumption from the Initial Fuel in the current fuel stint manually to adjust.

Longer RIS Outage

In case of a longer outage from RIS (rare but possible):

• All data previously received remains available in the software.
• You can still access stint/lap/fuel history and switch to manual calculations if needed.
• Once RIS comes back online, you can simply enter your last pit out lap in a new fuel stint — and fuel calculations will resume normally from that point.