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

Run activities showing brief pause

Recently when I look back at my outdoor runs every one shows a brief pause at some point during the run. I’ve checked auto pause is off and I’m certain it’s not me pausing the run. This mornings parkrun measured short again and when I look at the map the short period my run was paused mid run would explain the shortfall. It’s annoying and it makes all my runs look like I’ve stopped for a rest or to tie my laces.

I have a theory that it’s happening at the same time that I get the Perf Condition +/- screen (I think that’s what it’s called) come up. It’s as though for the few seconds my watch is displaying that screen it’s pausing me run.

Has anyone else seen this? Should I just turn off Perf Condition under Physiological Metrics? Or is there a fix which stops the pausing without losing the Perf Condition tracking?

my firmware is 11.60

  • Just to add… I’ve noticed now that these pauses are visible in my Runkeeper app and last between 2 and 4 seconds. Only once per run. But they don’t show up in Strava app. So maybe the Perf Condition is logged in the data somehow and Runkeeper is mistaking it for a pause. 

  • Hmmmm, I have performance condition turned on and don't experience a pause in the recording; unless I'm doing a very low HR recovery run that never triggers the performance condition screen, I get a +/- evaluation at roughly the same point on my route.  So I'd notice on the recording if there was a drop out occurring consistently at that mileage/time.

    Are you sure the recorded pause is happening at the same time as the performance condition "pop up" screen?

    Just out of curiosity, is the data showing a true pause (as if you pressed stop on the watch and then resume) or is it that it's recording as if "you tied your shoelaces"?  One would show a complete drop out in data and the other would continue to record heart rate but cadence and pace would show "0".

  • I’m not sure it’s recording it as a pause in Garmin connect but Runkeeper sees it as a pause on map view. It’s definitely the same place as I get the performance notifications. I’m starting to think it’s a Runkeeper problem where Garmin logs the time the notification happens and Runkeeper incorrectly interprets it as a pause. I guess we need another Runkeeper user to see if they’re getting the same issue. I can’t see any signs of it in Strava. Moving time and Elapsed time are the same in Strava.


  • Interesting and you may be right that Garmin is programmed to ignore the seconds it's collecting no data to show +/- performance.

    Although does Garmin Connect log a difference between elapsed time and moving time? If there's no difference then I think it confirms your assumption.

    Incidentally Strava is more forgiving regarding brief anomalies. There's time when I have to detour from the sidewalk to the street and when I slow down to run in between parked cars, Garmin will record a lack of movement. So my elapsed time and moving time are off by a few seconds. Strava ignores this discrepancy and makes elapsed and moving time the same.