TL;DR
Drivurs uses multiple run states because not every recorded run deserves the same trust level.
The important labels are:
- Valid
- Valid with warnings
- Invalid
- Incomplete
These are not cosmetic badges. They decide how the run should be interpreted.
Valid
A valid run is acceptable for normal comparison and best-time summaries.
This is the state you want when you are comparing changes or thinking about leaderboard relevance.
Valid with warnings
A warning means the run is still usable, but not perfectly clean.
The run may still be worth reviewing, but you should understand the warning before treating it as definitive.
Warnings exist so the app does not force a fake binary between “perfect” and “useless.”
Invalid
An invalid run should not be used as a normal benchmark.
It may still be interesting as history, but it should not be treated as trustworthy enough for best-time logic or serious comparison.
Incomplete
An incomplete run means the session captured something real, but the run did not reach a proper finish state.
This still matters operationally because it explains what happened in the session, but it should not be mixed with completed benchmark attempts.
Why this matters
Without these labels, people compare bad data and then blame the wrong thing:
- the tune,
- the part,
- the weather,
- or the app itself.
Validity labels are what make the viewer and leaderboard layers believable.
How to use the labels
- Use Valid for serious comparison.
- Review warnings before drawing conclusions.
- Keep invalid runs as context, not proof.
- Treat incomplete runs as session history, not final results.