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

Connect is switching moving time and time

On my two recent rides (Edge 510), Connect is reporting moving time as time. E.g., moving time and elapsed time are within seconds, and time is much lower (reflecting the time I had been moving on the bike). During my ride (before I saved it), moving time was the correct -- lowest -- amount.

What gives?
  • It's happening on the 520 too, shortly after firmware 6.20 hit, but not immediately after, as users report several rides displayed normally in GC after 6.20 hit. One poster was actually able to pinpoint the day and time the anomalies started occurring. It also happens when I record the rides with my Forerunner 235. The issue must be with GC and not the device or its' settings.

    https://forums.garmin.com/showthread.php?353978-Cadence-on-520-different-from-that-on-Garmin-Connect
  • Former Member
    0 Former Member over 9 years ago
    Same here. I updated yesterday, and my data for my run today was off. Moving pace is slower than average pace, and moving time is greater than elapsed time. This should be a pretty easy and timely fix, I'm hoping.
  • Another sample

    The problem is also happening to me. I'm using a Garmin Edge 800, and I don't think the change is related to a firmware change, since it hasn't changed in a while.

    My bike ride on June 25:3:23:31 Time
    3:23:12 Moving Time
    3:29:10 Elapsed Time
    16.5 mph Avg Speed
    16.6 mph Avg Moving Speed

    Note that Moving Time < Time and Avg Moving Speed > Avg Speed.

    My subsequent ride on June 29:2:47:16 Time
    2:51:36 Moving Time
    2:51:47 Elapsed Time
    18.5 mph Avg Speed
    18.1 mph Avg Moving Speed

    Note that Moving Time > Time and Avg Moving Speed < Avg Speed.

    I have another sample from July 3 like the June 29 sample (i.e., time and moving time appear reversed).

    I presume someone reversed the two time measurements in the sync process, or in the code on connect.garmin.com?
  • please log a case, let them know about this issue.
  • how do i 'log a case'?

    i just assumed someone from garmin read the posts on this forum to see what the issues are?
  • please log a case, let them know about this issue.


    how do i 'log a case'?

    i just assumed someone from garmin read the posts on this forum to see what the issues are?
  • Former Member
    0 Former Member over 9 years ago
    Thank you for the discussion on this issue. We have escalated these reports to the Garmin Connect team for further investigation and resolution. There are a couple of threads discussion this issue and we will post any new information or updates to this thread: https://forums.garmin.com/showthread.php?355419-Moving-Time-Wrong-Suddenly/page2
  • Thank you for the discussion on this issue. We have escalated these reports to the Garmin Connect team for further investigation and resolution. There are a couple of threads discussion this issue and we will post any new information or updates to this thread: https://forums.garmin.com/showthread.php?355419-Moving-Time-Wrong-Suddenly/page2


    thats great joseph, thanks. could you also get them to make 'lap swimming' editable again as many garmins over/under count pool laps and around 3 months ago it became impossible to edit distance, time, number of lengths etc. the only field that is now editable is calories. i used to be able to edit all fields.

    garmin really do need to sort out their code changing/testing process so that updates to connect dont negatively impact other features of the software. its a case of one step forward and two steps back with connect. connect needs to be properly tested before code changes are released. im on the brink of moving over the strava as connect is just too unpolished which is a shame as a brand like garmin should be leading the way with sports software.
  • will the moving time issue be fixed for everyone? I heard something about compatible devices and I only have an Edge 200.

    For now, I have been calculating the moving time based on data from the RideWithGPS app, which was usually close to Garmin's moving time. Hoping I don't have to do this anymore at some point. Also the difference between the elapsed and moving time and subtracting that difference from the time seems to be close too.

    thats great joseph, thanks. could you also get them to make 'lap swimming' editable again as many garmins over/under count pool laps and around 3 months ago it became impossible to edit distance, time, number of lengths etc. the only field that is now editable is calories. i used to be able to edit all fields.

    garmin really do need to sort out their code changing/testing process so that updates to connect dont negatively impact other features of the software. its a case of one step forward and two steps back with connect. connect needs to be properly tested before code changes are released. im on the brink of moving over the strava as connect is just too unpolished which is a shame as a brand like garmin should be leading the way with sports software.