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

Time of Workout is not correct

I just ran (started my Garmin 920XT at 11:32 am or so).
Uploaded workout to GC via mobile upload to GC Mobile.
My workout shows that it was started at 6:32 am. (correct day but the time is way off).
Looks like this has been happening for about a week or so.
I checked my settings in GC Desktop and the time zone selected is correct.
Is nobody else having this issue?
-FR
  • +1 on having this issue w/ my FR620. I think it may happen when an activity is edited or uploaded by the GC App on iPhone, but not sure. I seem to remember some activities, that just transfer via Wifi and I only edit in the web version of GC, don't seem to have this issue. I will test further and see if this is the variable on my end. Currently in PST I see an 8 hour offset. My workflow varies between uploading via Wifi and then editing the activity to add notes, etc. through a Macbook Pro in Safari or sometimes I edit in GC on my iPhone 4S, iOS 7.1.2.
  • Former Member
    0 Former Member over 10 years ago
    From the day we put the new features on the website does not work the sync from web to watch. See if they fix it soon.
  • +1 same issue on Fenix 2. It is adding the time zone offset (+11h) to my activities. As if it thinks the watch time zone is GMT.
  • Also broken for me for most of December with my ForeRunner 220.
  • This is very, very bad.
    And by the way ...... some of my "followers" have now commented that either the time settings are screwed up within Garmin Connect or I am training at some seriously off hours.
    My point ..... general public (i.e.- potential buyers) are now seeing flaws in the product.
    Really taking WAY too long to fix this fairly major problem.
    Strange it's not affecting everyone. Only certain time zones affected?
  • +1 on having this issue w/ my FR620. I think it may happen when an activity is edited or uploaded by the GC App on iPhone, but not sure. I seem to remember some activities, that just transfer via Wifi and I only edit in the web version of GC, don't seem to have this issue. I will test further and see if this is the variable on my end. Currently in PST I see an 8 hour offset. My workflow varies between uploading via Wifi and then editing the activity to add notes, etc. through a Macbook Pro in Safari or sometimes I edit in GC on my iPhone 4S, iOS 7.1.2.


    Further testing confirms that editing a run on the iOS Garmin app will offset the time stamp by 8 hours for me. This is confirmed and repeatable. WiFi upload from my 620 shows accurate time stamp details on the GC web site, but the moment the activity is edited in the iOS app and saved again, the offset occurs. I would gather anyone uploading their activities through their iOS device via bluetooth would have this issue as well. I'll test that as well on my next activity.

    I have reported this by email to Garmin. Hope they address it soon.

    Others are reporting this issue elsewhere in the forums.
  • Nice job figuring that out.
    I really hope they fix this!!!!!!
  • In addition to my email, I spoke to a Garmin rep on the phone today and made him aware. Had to troubleshoot another unrelated problem I am having with my 620 and took the opportunity to mention this issue. Hopefully they will take action soon. I think the more this is reported to them, the greater likelihood we have of it being addressed sooner than later.
  • OK, my theory is only partially correct based on today's testing. Taking WiFi out of the mix and only doing an unedited upload via bluetooth results in a correct time stamp for the activity. BUT, as soon as you edit the activity in the iOS app, the time stamp gets offset. So it appears editing and saving an activity in iOS is the culprit.

    I don't think I previously mentioned my details in case Garmin is reviewing this: FR620 (latest firmware), iPhone 4S, iOS 7.1.2 (GC app v2.8.0.14).

    Curious if anyone running iOS 8 on an iPhone 6 or 6+ is having the same issue.