Related

Pace and Running Dynamics Freezing

Greg Oliveira

Hi everyone.

I already have a ticket open with Garmin Support.

However, I’d like to know whether other Forerunner 570 users have experienced issues with pace data or other running dynamics during workouts. I’ve been using my watch for less than six months, and it is running the latest software version.

This issue occurred once last week and then again yesterday. Between those two incidents, I completed two running activities without any problems.

When the issue occurs, the current pace field freezes and displays 0:00/km. At the same time, power data stops being recorded. However, average pace and lap average pace continue to update normally throughout the activity.

Has anyone else experienced something similar or found a possible cause?

Top Replies

All Replies

  • 0

    Thanks for the post,  . I'm going to email you to gather some additional information on this, so please be on the lookout for that soon.  **

  • 0

    After the last update, I've had the feeling, a few times, that my PACE level is kind of stuck at a certain number for a few seconds, and my heart rate too. But I can't confirm that.

  • 0 in reply to Garmin - DK

    Hi,

    Did you send me the email? I didn’t receive it.

    The Brazilian support team replied and said this is probably a software issue. They asked me to reinstall the OS; however, the problem is still occurring.

    The freeze happens when I run faster than 3:50/km. I also discovered that if I pause and then resume the activity, the pace and other metrics start recording again.

  • 0 in reply to Greg Oliveira

     We did send an email to the GMail address tied to your forums account, which is also associated with your Forerunner 570/Garmin Connect account. That email was sent on June 17th, 2026--but I'm going to send another one your way now. If your email provider allows you to set safe senders, please add [email protected] to that list so our emails to you won't get filtered into your spam or junk mail folder.

    If anyone else is experiencing similar behavior with your Forerunner 570's Pace and/or Stride Length data fields freezing/showing 0.00 during an activity, please comment below. Thank you! 

  • 0

    Same problem with the Forerunner 970 and Fenix ​​8. Is it too much to ask for Garmin to finally fix the issue after five weeks? As it stands, the watches are useless to me!

  • 0 in reply to Garmin - KS

    I'm having the same issue. Disappointed It consistently happens when doing interval runs, like this:

    where there's a step with a pace target in the workout. This hasn't happened during any of my runs where I have a heart rate zone as a target, nor while tracking a bike commute (which doesn't have a target).

    The drop to 0.00 s/km seems to happen either directly at the start of the step:

    or immediately after:

    The pace line is also way too stable even when it isn't 0.00; I don't run this consistently. Sweat smile (This also only happens during the interval/pace tracked runs; it looks spiky as usual during every other run)

    For me, the average pace also appears to be recorded correctly; the post-step-report matches with what I think I'm running, and the 'Intervals'-tab in the app makes sense.

    The last interval run without this issue was on June 23rd; my June 30th run was the first in which this occurred, and it has been happening with every interval training since. Not sure if there was a firmware update in between, but I do normally update immediately when I get the notification. The 17.37 update I got yesterday at least didn't fix it, as the same issue occurred during my run this morning.

    I also turned on the Every Second Recording mode, but that didn't change things here.

    Hope this helps fixing it Slight smile

  • 0 in reply to Pjotter

    Have you tried to pause and resume the activity? This "fix" this problem. However, it can happen again.

  • 0 in reply to Greg Oliveira

    Managed to try that this morning, and that indeed works (though I had to to it for the first 3 or so intervals); it's obviously rather annoying that that's needed, but at least it tides me over until Garmin fixes the actual issue, so thanks! ^_^