Browse documentation
Setting a run's numbers aside
Keep a run that happened in your mileage and plan while telling your coach not to read its paces, heart rate or splits.
Sometimes a run was real but its numbers were not. You left the watch running through a stop, the GPS wandered under trees, the heart-rate strap slipped, or the treadmill counted more than you ran. Deleting the run would lose the miles and the day on your plan. Leaving it as it is lets your coach read paces and a heart-rate climb that never happened.
Ask your coach to set the run’s numbers aside instead. The run stays, and counts; its numbers stop being read.
What still counts
An excluded run keeps everything that says you did it. Its distance stays in your weekly mileage, your cardio load and the training history your plan is built from. If it fulfilled a planned session, that day stays complete.
What stops being read
Your coach no longer reads the run’s splits, its two halves, its heart-rate trend, or how pace and heart rate drifted apart. A run review names the exclusion and the reason in place of that split analysis. The run is never used as evidence for your Run Fitness — the single number your training paces come from — and its watch time is not taken as a race result: if the run was a race, give the official time and the race is recorded from that. A race you recorded from the run before setting it aside keeps the time it stored; ask your coach to correct that race if the time was the watch’s.
Choosing how far it reaches
Say why the numbers are wrong: the watch kept running, a GPS error, a heart-rate glitch, a treadmill that over-counted, or something else in your own words. Then decide about the score.
By default only the analysis is set aside. A planned session is still judged against its steps, and if the run already had an Execution Score — how closely it matched the session that was planned — that score stands. Ask for the score to be set aside too when the numbers it was built on are the problem: the stored score is removed, and the run stays unscored while the exclusion holds. Your coach cannot score it in the meantime, with the engine or by hand.
The run is marked wherever it appears
The run shows an “Excluded from analysis” badge on its page and in your Activities list, and the reason on its page, so a later review does not mistake it for evidence.
Putting a run back
Ask your coach to include the run again and its numbers are read as before. A score that was removed does not come back on its own; ask for the run to be scored afresh.
When to delete instead
Set a run aside when it happened and should count. Delete it when it did not happen, or is a second copy of a run you already have. Deleting and restoring is its own action; see the page on deleting and restoring activities.
Ask your coach
“I left my watch running through a bathroom stop on Thursday — don't learn anything from that run, but it still counts.”
“The GPS was all over the place on my trail run; ignore its paces.”
“Put that run back, I've fixed the heart-rate strap.”
Related
- Deleting and restoring activities — Hide an incorrect activity from local history and training calculations, or restore it later without changing the original provider record.
- How a run is scored — See how your completed run is compared with its planned session and why some runs correctly have no score at all.
- Understanding Run Fitness — Read your current running-fitness evaluation, its evidence and confidence, and the race equivalents and workout paces it helps produce.
Last updated