Moving Time Wrong Suddenly

No idea...

Garmin?

Tks

@marcossaad_

You are the first report that we have seen where the moving time is still incorrect. Thank you for posting a link to the activity. We have sent this information on to the Garmin Connect team for further investigation to determine why the information is still displaying incorrectly for you.

How do we fix activities uploaded during the bug?

I uploaded an activity last night and the graphs are the correct length. Earlier I discovered that if I toggled elevation correction on/off for older (pre-bug) activities that that would be corrupted. I assumed that once the bug was fixed I would be able to fix these activities as well as ones uploaded during the bug by toggling elevation correction which causes the graphs to be re-drawn. This doesn't work, the graphs are still based on "elapsed time".

So, how do we fix activities corrupted by the bug without deleting and re-uploading?

I uploaded an activity last night and the graphs are the correct length. Earlier I discovered that if I toggled elevation correction on/off for older (pre-bug) activities that that would be corrupted. I assumed that once the bug was fixed I would be able to fix these activities as well as ones uploaded during the bug by toggling elevation correction which causes the graphs to be re-drawn. This doesn't work, the graphs are still based on "elapsed time".

So, how do we fix activities corrupted by the bug without deleting and re-uploading?

Ive tried deleting and uploading 2 activities but it doesn't fix the problem, it just changes it.

On the first activity I deleted and uploaded, the first mile split (for a trail run) the average pace was 10:38 and the moving pace was 6:14. Which is quite flattering but in all honesty is probably faster than I have ever run in my life! The other splits for the run looked OKish.
On the second activity I uploaded (which is again a trail run) for the first mile split the average pace was 8:54 and the moving pace is displayed as -- (no figure given). For the second mile split the average pace was 8:59 and the moving pace was 5:29 a time I could never aspire to under any circumstances let alone running across fields and through woods. The average moving pace for the whole 7 mile run was 6:50. A time I have never achieved even when doing a road run.

I gave up at this point

I also tried to delete and re-upload an activity from July 30th (still broken for me) and that didn't resolve the problem. I did not collect the original .fit file from the Fenix3 to re-upload so I might try that later.

We appreciate the discussion, and have passed along this information to the Garmin Connect team, indicating that users are still seeing this issue when uploading the activities again. The investigation of this is still ongoing, and we will provide an update when new information is available.

We appreciate the discussion, and have passed along this information to the Garmin Connect team, indicating that users are still seeing this issue when uploading the activities again. The investigation of this is still ongoing, and we will provide an update when new information is available.

Not all users Joe. This issue is now fixed for me, and I assume for others too.

Tom

I am still experiencing the Moving Time issue; the first 1/2 miles of runs are not being timed. Here are a few activities if it helps troubleshoot -
https://connect.garmin.com/modern/activity/1285648080
https://connect.garmin.com/modern/activity/1287233267

still wrong mov time and enabled elev corrections

Hi,

Still getting messed figures. (https://connect.garmin.com/modern/activity/1291571975)

3:09:24
Time
3:36:10
Moving Time
5:08:23
Elapsed Time

Please, can somebody tell what "TIME" stands for?

and why Fit History on the watch doesn't even show moving time? (picture attached)



also the annoying Elev Corrections Enabled when shouldn't be...

Regards,

What is this 'Moving Time' thing and why is it different from 'Time'??

Here's an example from my run today:
[table="width: 500, class: grid, align: right"]
[tr]
[th]Splits[/th]
[th]Time[/th]
[th]Cumulative Time[/th]
[th]Moving Time[/th]
[th]Delta between 'Time' and 'Moving Time' (in sec)[/th]
[/tr]
[tr]
[td]1[/td]
[td]8:06.7[/td]
[td]8:06.7[/td]
[td]8:03[/td]
[td]3.7s[/td]
[/tr]
[tr]
[td]2[/td]
[td]7:40.2[/td]
[td]15:47[/td]
[td]7:34[/td]
[td]6.2s[/td]
[/tr]
[tr]
[td]3[/td]
[td]7:32.3[/td]
[td]23:19[/td]
[td]7:28[/td]
[td]4.3s[/td]
[/tr]
[tr]
[td]4[/td]
[td]7:52.7[/td]
[td]31:12[/td]
[td]7:47[/td]
[td]5.7s[/td]
[/tr]
[tr]
[td]5[/td]
[td]7:54.9[/td]
[td]39:07[/td]
[td]7:49[/td]
[td]5.9s[/td]
[/tr]
[tr]
[td]6[/td]
[td]7:49.8[/td]
[td]46:57[/td]
[td]7:44[/td]
[td]5.8s[/td]
[/tr]
[/table]

Needless to say, I did not stop at any time during this run; nor, to be quite clear, did actually pause my Garmin. So why is there a discrepancy between 'Time' and 'Moving Time'?

--Sam