Inaccurate distances when corrected, completely destroy timings....

[jwerdna]

I have encountered a huge problem today having completed the Swim Serpentine event in London. Distance was incorrectly showing as 2,745 metres instead of 3,440 metres. However, when using the 'correct distance' feature, the distance correctly changes to 3,440 metres, but my moving time drops from 1hr 37mins to 22mins! A drop of 1hr and 15 mins!! What is going on here Strava??

Please just add the ability to show elapsed time rather than moving time, and the problem would be significantly less of an issue. 

Especially when these events could be classified as a 'race' as per the options for running and cycling...

[Jan_Mantau · Accepted solution]

There are some threads about that already, unfortunately Strava doesn't want to admit that their calculations are completely wrong. But here is a workaround to correct the moving time after it was garbled by the "Correct Distance" feature: You can change the activity to Run, save and then change it back to Swim. This keeps the corrected distance but reverts to the original moving time. Please note that Strava needs some seconds after changing activity types to display the new values correctly.

Original: Wrong distance, correct moving time:

After "Correct distance", the moving time is wrong:

After changing to Run and back to Swim everything is okay:

[jwerdna]

Thank you very much for the workaround! Appreciate it 🙂