Elapsed time incorrect

This has happened on multiple devices (FR945/Fenix 5x/Fenix 6S) and therefore multiple softwares. On multiday events, I often stop the activity while at aid stations, then continue when I begin moving again. Almost every time, this results in an Elapsed time that is much less than the total even time. It makes no sense to me or Garmin support. The total elapsed time can be easily calculated by subtracting the starting time of the activity from the time when I finish, but this screws up my race time and results in GC, TP, Strava, etc.

My theory is the following: When I stop the activity at aid stations, I usually lap while on the stop screen. I'm wondering if that affects the Elapsed time calculation? I've tried to test this on shorter events and it doesn't seem to affect it, but maybe on multi-days it does?

Has anyone else had a similar issue? Any theories?

0 tmk2 over 3 years ago

Can you provide an example of what you're seeing? Like the start time of the activity, the end time of the activity, and what your garmin shows you as elapsed time.

I've never done multi-day activities, but I can imagine that the easiest software mistake would be doing the math on time-of-day only, without looking at the date. This way it would work properly on one-day events, and incorrectly on multi-day events.

0 gaijin over 3 years ago

Not sure we are all talking about the same times.

Here's the Timing summary for a Bike Activity I did over two days:

The "Time" 1 Hour:46 Minutes:49 Seconds is the Activity Time reported in the Activity Summary on Garmin Connect

The "Moving Time" is the Time minus any stops.

The "Elapsed Time" 25 Hours:11 Minutes:02 Seconds is the total time from the beginning of the Activity to the end of the Activity.

Looks to me that the "Elapsed Time" in the Garmin Connect summary is correct, but sounds like in your case Garmin is reporting the "Time" when you want it to report the "Elapsed Time."

HTH

0 mwavs over 3 years ago in reply to tmk2

I should have clarified, this does not happen on all muldays

This one was over the time change weekend, so who knows.

https://connect.garmin.com/modern/activity/6427714124

Elapsed time should have been 41:38:xx

https://connect.garmin.com/modern/activity/4491550077

Elapsed time should have been 50:22:xx

This was a single day.

https://connect.garmin.com/modern/activity/3168206128

Elapsed time should have been 12:28:xx

0 Dr Phil over 3 years ago

Are you using Ultratrac?

0 mwavs over 3 years ago in reply to Dr Phil

Oh god no. Ultratrac is less than useless. Lol. But that is interesting... I would have connected the watch to a charger during the activity on these events. But I haven't seen the elapsed time mis-match on many other events where I use a charger mid-activity.

0 gaijin over 3 years ago in reply to mwavs

mwavs said:
I should have clarified, this does not happen on all muldays

This one was over the time change weekend, so who knows.

https://connect.garmin.com/modern/activity/6427714124

Elapsed time should have been 41:38:xx

https://connect.garmin.com/modern/activity/4491550077

Elapsed time should have been 50:22:xx

This was a single day.

https://connect.garmin.com/modern/activity/3168206128

Elapsed time should have been 12:28:xx

OK. Ignoring the first activity which occurred over the time change weekend, we have the following two:

"Elapsed time should have been 50:22:xx" and Elapsed time is reported in Garmin Connect as 50:21:25 - looks good to me, is this a problem?

"Elapsed time should have been 12:28:xx" and Elapsed time is reported in Garmin Connect as 12:20:14 - looks good to me, is this a problem?

I guess I don't see where the "few hours too short" error comes into play...

By the way, how do you arrive at the "should have been" elapsed times?

0 mwavs over 3 years ago in reply to gaijin

Why are we ignoring the time change? It’s not off by an hour or something simple. I’m not sure what your criteria are, but 1-8 minutes can be important in a race.

Here’s another over 35 mins discrepancy.

https://connect.garmin.com/modern/activity/3940540627

I pressed start at 5am Saturday and pressed Stop then Save at 12:12pm Sunday or 31:12:xx elapsed time.

0 Former Member over 3 years ago in reply to mwavs

So, you're talking minutes (1-8 and 35 on another) and not a "few hours" like your thread title says?

0 gaijin over 3 years ago in reply to mwavs

mwavs said:
Why are we ignoring the time change?

Because you said, "This one was over the time change weekend, so who knows."

If you don't know, I wouldn't even try to guess...

0 gaijin over 3 years ago in reply to mwavs

mwavs said:
Here’s another over 35 mins discrepancy.

connect.garmin.com/.../3940540627

I pressed start at 5am Saturday and pressed Stop then Save at 12:12pm Sunday or 31:12:xx elapsed time.

That activity was with a Forerunner 945 in August 2019 - more than 2 years ago!

WTH?