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

New Garmin Connect showing incorrect elapsed time and lap averages

Today was the 1st time I uploaded after the site upgrade (I had done so last Monday and that activity showed just fine). Today's activity elapsed and moving time are incorrect and much higher than what they actually were. The watch's history shows time of 38 mins and a bit. Garmin Connect shows... 42:17 and 42:12, and adding the lap numbers makes no sense.

http://connect.garmin.com/activity/448385332#



The lap times are all in the mid 5s min/km, yet the average shown is 6:02.

Split Time Distance Avg Pace

1 6:06.4 1.00 6:06
2 5:31.0 1.00 5:31
3 5:16.6 1.00 5:17
4 5:16.3 1.00 5:16
5 5:20.9 1.00 5:21
6 5:16.1 1.00 5:16
7 5:12.4 1.00 5:12
8
Summary 42:17.0 7.00 6:02 ->> makes no sense, look at all the 5s above -> 38 mins

I delete the activity and resubmitted, same deal. I know my pace was indeed in the mid to low 5mins/km.


Has anybody else seen this? Any suggestions? Garmin 405.
  • Former Member
    0 Former Member over 11 years ago
    Same here. I'm getting fed up with Garmin. Have been a loyal customer and advocate for years, but starting to lose patience. Absolutely no communication from them either.
  • For me changes and the emergence of the low bad speed from January 5; until then, everything was well calculated. Whether such a difficult change time from which the average speed is calculated (Moving Time, not Elapsed Time)?
  • Former Member
    0 Former Member over 11 years ago
    I really can't believe this. How can my forerunner 305 say one thing and the website something totally different. The times are not even close. This effectively makes everyone's forerunners with this problem totally useless with Garmin Connect. Time to go somewhere else. This issue cannot be that difficult for Garmin.
  • Former Member
    0 Former Member over 11 years ago
    Has anyone called the Garmin Customer Service yet? If so, what did they say about the issue? Let's all make a point to call tomorrow and get some sort of update on where this is at. This is not that difficult of a bug to work out...
  • are the newer devices like the 620 also being affected by this?

    I hope these website issues aren't garmin's way of trying to push us to buy newer devices
    I'm not a software expert but when something's worked perfectly for 4 years, and now seemingly basic problems are taking over 3 weeks with no sign of a fix in sight
  • Former Member
    0 Former Member over 11 years ago
    Guys - can you not look at other posts in the forum - there is a sticky post for this 3 from the top of the forum - https://forums.garmin.com/showthread.php?74645-Time-Calculation-Issue


    i`ve just checked your link and it says the error has been corrected, yet i`ve just uploaded a run i`ve done today and its knocked 10 min off my actual time. obviously hasn`t been fixed then. forerunner 305.
  • Former Member
    0 Former Member over 11 years ago
    nope, its still not fixed as of march 14 (even tho the website says it is). pull out a paper and pencil and add up the split times... they won't equal the total as shown on garmin connect.
  • Definitely still not fixed despite the message on https://forums.garmin.com/showthread.php?74645-Time-Calculation-Issue
    They've just changed the bug behaviour so instead of making your overall time slower it now looks faster. According to Garmin Connect elapsed time my recovery jog this morning (about 9km) was run at world class 1500m pace, smashing the 5000m world record along the way!
    What actually happened is that I paused my FR 405 for around 20 seconds when I encountered a flooded footpath and pondered what route to take. Garmin Connect processed all of the splits showing the correct (slow) paces, but the overall activity stats only took the elapsed time from the last 19mins after the paused period.
    Failtastic.
  • Former Member
    0 Former Member over 11 years ago
    Mine has just started having this issue. Very frustrating. I'm having to go back to my watch and edit all of my data uploaded to Connect. I don't want to do that!!!!1