Incorrect Paused Runs on Strava

[nycjoker]

Strava and Fitbit Surge integration has been working great until recently. Paused runs are no longer represented accurately on Strava. The issue is not only a display issue but also impacts pace calculations. This worked well earlier in the year and I'm curious if Fitbit made a change that impacts their partner, Strava.

Example: Pause at mile 3 marker for a few minutes. Take a look at mile 4.

Fitbit - Map

Fitbit - Splits

Strava - Map

Strava - Splits

I have performed this test several times at various locations and confirmed this is an issue. I'm guessing Fitbit made some change to how data points are collected in TCX file and updated their system to understand this data properly. However, partners such as Strava do not have this custom logic.

I'm hoping someone for Fitbit can dig into this issue and work with Strava to capture and represent data accurately.

[SunsetRunner]

Fab @nycjoker

Moved your post from the Surge to the Third-Party Integrations section since being more relevant to the topic.

Your post will get more attention here.

Wishing a wonderful weekend

[nycjoker]

Thank you. I have also opened a case with Fitbit Support on this topic.

[SunsetRunner]

Did this ever get fixed? I am having the same issue.

[nycjoker]

I have been repeatedly contacting Fitbit support to get an update on the open case. No one is providing any information on when this issue will be addressed. Terrible!

I have daily runs that show up correctly on Fitbit's dashboard and incorrectly on Strava whenever pause is used. Fitbit should put out a notice that the Strava integration has a huge problem.

Here is my run from yesterday. I paused shortly after Mile 1. The pace is completely wrong for Mile 2, the map is wrong (I guess a swam a bit too), and now all my stats for this route are wrong on Strava since this impacts the overall pace.