It looks like there has been a change introduced in how the pace is being displayed for running activities.
Before the change, the pace for splits would be shown as moving pace (i.e. ignoring for example pauses at traffic lights). Now, any pause is reflected in the pace, resulting in uneven outcome.
When I checked my recent runs, I saw that an October 5 run was still recorded as expected, but next run from October 7 and all runs since then have the splits pace all over the place.
Is this a bug or an intentional change?
(Recording my runs with the native Apple Watch Workout app and importing from Apple Health to Strava via the iOS Strava app.)
Solved! Go to Solution.
Hi, a notification popped up on me that someone commented on my post - @rkleine, I think the issue you described is yet something else. The original bug I reported is already fixed, I’m not experiencing the problem anymore. But indeed what’s displayed on your run looks odd - the avg pace shown on the Strava record is 3:51/km (which seems to be correct - matches the Watch splits), but all the splits are well above that average… perhaps submit a support ticket..?
Just in case anyone else experiences this - Support replied and indeed it’s a bug, hopefully will be fixed soon:
This is a known issue specifically related to newer Apple Watch devices. Basically, we had them added into our device database but there was a separate database they needed to be added to which allows proper parsing of activity data in the FIT files Apple sends us.
We hope to have this resolved as soon as possible.
Thanks for posting about this and apologies for any confusion. I'm not aware of any recent changes with this, so I'm going to escalate this ticket to our Support Team so someone can take a look at your activities and troubleshoot with you.