Related
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

Since buying Forerunner 645 Music the transfer of data between Garmin Connect and Strava is inaccurate as Strava takes into account some of my static time when the watch was paused. I've only had this issue since using the new watch.

5792696
over 4 years ago

For example: I do an 8km run at 4.21min/km pace in 35.00 minutes, with 5 minutes of static time where my watch was paused (crossing roads, opening gates etc). The run shows my average pace to be the time that my watch was un-paused on the Garmin Connect app, however once it has transferred to Strava, the file will include per say, 1min30secs of the static time when the watch was paused, therefore decreasing my average pace to 4.34min/km. The transfer to Strava does not include all of my static time, but always a portion of it. Has anyone had the same issue as I would quite like accurate data back! Thanks

  • 0 over 4 years ago

    My only thought is whether you are importing it into Strava as a 'Race'.  If it's a race I think it includes the whole time.

  • 0 over 4 years ago in reply to Winbatch

    It is just recorded as a normal activity, and doesn't include all of the elapsed time, just some of it. Thanks for trying though!

  • 0 over 4 years ago

    Here is what I've noticed, maybe it can help you. If I use AutoPause on the watch, and I NEVER manually pause during a run, then Stava will only use moving time. (This is generally what I want)

    If I use auto pause, and I manually pause even once, then Strava will count the auto paused time as moving time.

    I think a variation of this also happens when you aren't using auto pause. If you never manually pause, Strava will only use moving time. If you manually pause even once, Strava will use your unpaused time as moving time.

    In summary: I choose to only use AutoPause or always pause manually, but not both on the same run.