Strava export not correctly recording pauses

Yurgo

@Dimitrios-Kanellopoulos said in Strava export not correctly recording pauses:

@Yurgo got it thanks! I ll update you on this but lets discuss this here, as this thread is not for swimming. (trying to keep the scope).

Short update this is under fix (swimming) and I do hope next week to be ok

Many thanks!!

A Former User

@Dimitrios-Kanellopoulos
First of all, I am very relaxed myself.
I did not call you buddy or asked you to relax yourself.
The rest of your logic or mine I fell should not be discussed any further.

Šón Čestr

@Dimitrios-Kanellopoulos , yep, I was also referring to the splits (and corresponding pace graph) that are auto-generated by Strava. I use the web version and see them here:

a) On the overview page: “Splits” in the right-hand panel beside the map and pace graph in the bottommost panel

b) Analysis → Workout Analysis → Bottom left panel when viewing “Splits” or “Smoothed” but not “Laps”

Dimitrios Kanellopoulos

@Šón-Čestr clear! The fix is coming for that.

And it is related to your nice finding of pauses.

So just following up, we export also the data during the pause period and that makes strava count very strange split times.

I am sure this fix will rollout next week as I said about swimming as well (that is a different fix though) if all goes well.

Šón Čestr

@Dimitrios-Kanellopoulos nice! You guys fixed this quickly! Thanks!

D Schilderman

@Dimitrios-Kanellopoulos
Thanks for your reply. So I can expect the fix within a couple of weeks :).

One more question. Does that fix also correct for “auto-pause” when standing still? Or only manual pause.

Edit:
To add… I just checked the details of the run that I originally was talking about.
The Suunto App also shows 29 mins for the 4th km where I had my watch on pause… So do we get a fix for that AND strava?

Kind regards.

Dimitrios Kanellopoulos

@D-Schilderman the fix for the app (presumably android) I am not sure about next week.

Can you elaborate on the autopause thingy about strava? The moving time vs elapsed time ?

D Schilderman

@Dimitrios-Kanellopoulos
Well… I had autopause turned on but i also manually put it on pause also during the period that we were doing drills.
So a double whammy (manual pause + auto-pause).

It still registered all the time on the suunto app and strava.

Dimitrios Kanellopoulos

@D-Schilderman for strava to remove these pauses (on the total time) you should not pause the watch.

Strava will do it’s calculations if there is no watch pause event.

D Schilderman

@Dimitrios-Kanellopoulos So until the fix in a few weeks, this is the way to do it…?
Thanks!

Dimitrios Kanellopoulos

@D-Schilderman About the total time (and not the splits that this thread is about) we cannot do anything. That is how strava works and how people are used to it. Once we “hacked” it and people complained why strava does not calculate the moving time

SamanthaJ

Please can you advise, my moving time and elapsed time when imported to Strava both reads the same (watch is Suunto Spartan Trainer Wrist HR). This watch is new and previously I had a Ambit 2 with no issues. I never paused the Ambit 2 due to always receiving the difference between moving/elapsed. I thought it would be the same on Spartan Trainer.

SamanthaJ

@SamanthaJ All good, think I have just worked it out ‘Autopause’ ‍️

Dimitrios Kanellopoulos

Hi this should be fixed as of today.
Paused records are no longer included and that should fix the strava autogenerated splits

Dimitrios Kanellopoulos

Sorry not yet deployed. I made a mistake.

Jack Davis

I would like to flag this as an issue as well and I don’t believe it’s ‘Just how Strava works’. My partner has a Garmin watch and if she pauses her watch her split on Strava only shows the moving time whereas if I pause my Suunto run it incorperates the pause into my split on Strava.

Dimitrios Kanellopoulos

@Jack-Davis hi Jack this issue is about splits not the total moving time. I own a garmin as well and it does work as Strava explains it here:

https://support.strava.com/hc/en-us/articles/115001188684-Moving-Time-Calculations

When uploading runs Strava relies on the recorded “timer time” which is the time the app or device was unpaused to determine moving time. As long as your device is recording conventional pauses, Strava will respect any pauses recorded in the file whether your device pauses automatically or you manually hit the pause button. It’s important to keep in mind is that if you choose to pause you must do so consistently. If there are any pause events in your activity file our server will not remove any additional resting time. If you do not pause at all our server will calculate moving time based on the recorded GPS data. Again, even though elapsed time may be the same, Strava may calculate moving time differently than other platforms.

Jonathan Newby

@Dimitrios-Kanellopoulos you own a garmin🤭

Dimitrios Kanellopoulos

@Jonathan-Newby I test competitor watches. I am a fieldtester
You can ask me anything about it

Šón Čestr

Here’s another strange, related sample:

https://www.strava.com/activities/2459472037/overview
https://app.suunto.com/move/seanchester/5d0894c88bfe5dc4be4e4aec

This activity contains no pauses. However, Strava (the Suunto export) and my watch both report 320 metres longer than does the Suunto app. In Strava, the pace goes wonky in those last 300m, and it reports a personal fastest 1km time when I was just jogging. GPS reception was spotty in the middle of the run (despite open skies), but I take speed/distance off the Stryd footpod. I had FusedTrack enabled.