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

Huge timegap in the middle of my run

Former Member
Former Member
My run on the weekend caused a rather interesting error/bug. When I went to check it out it shows the right stats (time/distance/avg, etc) but when you try to look at the graphs, it shows that my 2hr:17min run took 528hr:30min (moving time). Before the 'gap' and after shows the right info (when I zoomed it to see what the ***) but the middle is a straight line of my over all average. Any ideas how to fix this easily? Not a big deal but would like to actually evaluate my run instead of messing around with the zoom multiple times just to check it out.


The Summary (and yes I know the 'best pace' is never right for me):
2:17:01
Time

538:28:50
Moving Time

2:17:01
Elapsed Time

6:27 min/km
Avg Pace

0 min/km
Avg Moving Pace

2:22 min/km
Best Pace
  • Former Member
    0 Former Member over 8 years ago
    The same thing happened to me. See here

    I just bought this watch, and this is the first time I've run with it. There were major flaws with the GPS as well - basically the entire first four miles were off. (I don't run 6:45-minute miles.) I don't know what causes it, but I'm wondering if my watch is broken.
  • Former Member
    0 Former Member over 8 years ago
    I submitted a response to this post several hours ago. It's still in moderation purgatory. I don't know whether that is because I included links or because I'm a new forum member.

    Anyway, I purchased a Forerunner 235 this week and did my first run with it this morning, and the same thing happened as happened to you. It was a 4.5-mile run, and the watch thought the third mile took about 4,500 hours (189 days; as a result, it actually dated my run March 16, 2016).

    In addition, there were severe GPS glitches, resulting in the first two miles not appearing on the map at all, so maybe my watch is just very defective (I have written to Garmin Support), but it's possible that the "moving time" glitch is a software issue that affects multiple users.