On my long run today I was closing in on 15K, but as the lap stats appeared on the screen it had jumped directly past 15K to 16K.
Since I was using navigation on this run I hoped it would somehow "figure out" the error and revert to correct distance since it was still leading me correctly on the final part of the route.
This however didn't happen, so the watch now insists that I ran 17K rather than the actual 16K.
Strava had the best and easiest way to correct this according to the route, which also means that the erroneous km in pace 0:00 vanished by itself.
In Connect I can do the manual correction of distance (which I did), but aside from the overall pace getting right, I don't know how this affects the rest of the stats as this isn't clear?
Also, most annoyingly, it doesn't transfer back to my watch despite sync, which is what my running program from Runna is communicating with and therefore affected by.
I've only had the watch for eight weeks but it was the 35th run I did with it and it is the only time this have happened. Don't know if it's related to the newest software update but would hate for it to happen again, and would appreciate a solution for useful correction since this should be doable.