Moving Time Wrong Suddenly

While I love my VivoActive I am astonished by how poor the Garmin Connect service functions, when it does actually function. This is a major bug that should never seen the light of day. Is there even any regression testing of this software? This screams of poor QA, no way a basic calculation should be this wrong. And total lack of any workaround? Inexcusable.

Has anyone found a manual way to fix the Garmin Connect Autopause issue? Is there any other apps or websites out there that can manually pull the data from a Garmin device and post the correct speed and time data?

Is there any word on when Garmin will have a fix or at least a workaround? This seems like something that is simple to fix. When it is fixed I hope they provide a tool to correct the months worth of data that we have all had corrupted.

the only way for now is to manually switch to showing the data By Distance in stead :(

Same here... I noticed the moving time being higher than the total time... which is odd...

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

I'm having trouble with this issue as well. Moving time is showing as more than elapsed time, which is simply not possible in this space-time continuum. Average moving speed is showing as 30~% slower than average speed and is inconsistent with 5 prior years' of data I have in Garmin Connect. It's hard to see how this error could have ever slipped through to production, and it's even harder to see how it could go on uncorrected for this long. While I like my device, Garmin's lack of fix for this shows an apparent indifference that's quite frustrating.

Garmin supports know about this issue already. will be fixed "soon".

I ride almost every day and it has been wrong since last Thursday (6/30) for sure. I didn't ride on the 29th and I saw another post that's when he noticed it so that's probably the day when this happened. This goof doesn't apply to any single device. Everyone I follow has the same issue and we have different devices so this has to be a Connect issue.

I've set auto-pause on a Edge 510.The change happened on June 29. Prior to the 29th the "Total" was within 1 minute of "Moving Time". On the 29th and after "Moving Time" is within a minute of "Elapsed Time."

After all this time wrong mov time ... what´s "TIME" anyway

Hi Guys,

After all this time we still get wrong info for MOV TIME on the watch, on GC as well GCM...
Also, I'd appreciate the definition of field TIME.

From my last activity:

TIME=2:20:17 (this should be moving time...)
MOV TIME= 3:35:00 ( this should be the ACTIVITY elapsed time...?)
ELAP TIME= 3:36:10 ( time since GPS was turned on?)




Thank you,

Garmin supports know about this issue already. will be fixed "soon".

I hope they announce the fix when they do fix it.

I hope they announce the fix when they do fix it.

At the bottom of the Garmin Connect web page it states the current version is 3.8.1.1. Could it be that June 29, 2016 was the implementation date and that rolling back to version 3.8.1.0 would solve the problem?

wrong elapsed time

yes i rode today ,i was actually away for over six hours

garmin connect shows
Accumulative 5.14 mins
time 5.14 mins
moving time 6.18


tue data is
Accumulative time 6.18
time 5.16 give or take a minute normally
moving time 5.14 as this was my actuall riding time.

spoke to garmin today who are aware of issue but no time scale to putting problem right.

the question is why have an expensive data colection device thats works perfect and uploadable to enable the data to be analysed when garmin connect basically jumbles everything u,p the data collected today shows me completing ride of 81.2 miles at a rate of average speed of 11.3 average mph actually it almost 16.average mph . so how good is garmin connect at calculing data currently not as good as an abacus (a frame of diffferent coloured beadds used to calcuate sums of data chinese i think) come on garmin i know is summer but please get your finger out. and sort it out.