This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Splits times totals incorrect

sm_runner2011 over 11 years ago

The past few uploads the total time on the run was incorrect at Garmin Connect site but is correct on watch (410). Sample...
I did a 5.63 mile run and the watch had the total time of 53:07 which was correct, but after upload and checking it out at the Garmin Connect web site the splits show 1:04:56.

0 Former Member over 11 years ago

While this is not helpful, my watch has started doing the same thing over the past 4 times I have used it. Today my watch said 7km in 40.59 but when I downloaded it onto Garmin Connect it said 43.23. I have been manually editing the time on Garmin Connect. Very strange and annoying.

0 Former Member over 11 years ago

I'm having the same problem- Go for a run, have to take a phone call in the middle of it, stop Garmin (because, of course), restart watch and finish run. At the end, my watch displays the correct time that I ran, but when it uploads, the time defaults to the elapsed time and I have to manually correct it. Annoying and frustrating. This has happened every run over the last week or so and it has happened while using both my 205 and my 410. Can this be an issue related to the recent website update/upgrade?

0 travis.vitek over 11 years ago

Can this be an issue related to the recent website update/upgrade?

Yes. It is most likely due to a problem with the Garmin Connect website. If you use another 3rdparty website to track your workout data (Strava, ...), they all display the correct times.

Travis

0 Former Member over 11 years ago

Bump... Garmin, fix this already!!!

0 sm_runner2011 over 11 years ago

Yes. It is most likely due to a problem with the Garmin Connect website. If you use another 3rdparty website to track your workout data (Strava, ...), they all display the correct times.

Travis

yep www.mapmyrun.com works fine.

0 Former Member over 11 years ago

an administrator reported in some thread that it would be fixed during next upgrade 1st week of april. lets keep running and knock on wood in the meantime!