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
    I have just uploaded my last week's runs to Connect and are seeing the exact same issue. I have a Garmin 305.

    My pace per lap all looks fine and matches the data on my device but the total time is bigger than the sum of the individual laps so the overall pace calculation is incorrect. Distance is fine.

    It looks like the time when I pause the device is being counted into the overall activity time so pace is calculated on the time between starting the activity and its final finish regardless of any pauses along the way. Connect is using total time rather than moving time whereas until this update any paused time would be removed from any calculations. Very frustrating.
  • I have exactly the same issue - for me Time is the same as Elapsed Time and is incorrect. This is no good for any kind of interval session. I wonder if it relates to the new garmin connect rollout as some display elements have changed also. I have a 405CX
  • Going back to my previous runs, they are all shown wrong since about February 12, same issue. I use these numbers shown by Garmin Connect to enter them into a different system, they are all wrong.
  • Former Member
    0 Former Member over 11 years ago
    Same thing with a 405.
    I believe it is a bug. I don't really care what is the time elapsed from start to finish, if there is a pause, the pause should not be counted.
    Is anybody from Garmin reading these posts?
  • Former Member
    0 Former Member over 11 years ago
    I've been having the same issues for the last week or so. Timing data displaying on my Garmin Connect does not match the data on my device. Forerunner 410.

    How do we bring this to the attention of somebody in charge at Garmin Connect?
  • Hi guys,

    I have the same problem!!! When I run I must stop my FR305 in the traffic lights for example, when I upload the race to Connect moving time are incorrect.

    Maybe the problem is due to migration to new web plataform, any solution?
  • 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
  • Former Member
    0 Former Member over 11 years ago
    About a week ago I uploaded my 405, and saw that on 4 runs, TIME = MOVING TIME = ELAPSED TIME, which was not the case. Obviously, the PACE was higher than the way it was previously calculated. There was no change when I turned on the AutoPause feature. This is clearly a Garmin Connect issue, not an issue with the 405, because I let Strava upload the Garmin data and Strava correctly identified TIME, ELAPSED TIME and PACE correctly. So now I use Strava for the correct data...
  • Former Member
    0 Former Member over 11 years ago
    I am having the exact same problem. Just ran 13 miles, watch says 1:50, Garmin Connect says 2:12. This just started a week or so ago.
  • Former Member
    0 Former Member over 11 years ago
    Same problems with the 410. Started happening just over a week ago.