Hello @Jeroentje
Thanks for posting about this. I'm a little confused about what's happening. Are you saying that the moving time you see on Strava after your activity syncs seems incorrect, because we are not removing your stopped / paused time?
Thanks so much for clarifying this.
Yess,
Moving time and Total workout time are the same If you use the Apple Watch running workout and sync this with strava app on iPhone.
Hello @Jeroentje
Thanks for clarifying what's going on. I looked into this and it is a known bug.
We're currently investigating this issue and we apologize for the inconvenience. The discrepancy you're seeing is due to the paused events that occur in the activity file. Going forward we would recommend NOT manually pausing your activity when you're recording with the Workout Watch app. When your activity is imported, we will calculate your moving time based on the GPS data being recorded.
Alternatively, if you need to pause your activity while you're recording, you can record with the Strava Watch App. This article can provide you with more information on how you can set this up.
I'll post an update here when this issue is resolved. In the meantime, please use one of the two workarounds suggested above and be sure to let us know if you have further questions.
I am having the same issue. I’ve always ran using apple fitness which syncs with strava. I don’t manually pause but usually when synced strava has the moving time with any stops at roads etc removed and the elapsed time. However, recently they are both the same when I’ve definitely stopped for periods, sometimes of 1 min plus. Any updates on solutions to this? Thanks
Hello @Aileenb and @Jeroentje
I wanted to update you both on this issue. It is still unresolved and is in the hands of our Engineering Team. In the meantime, we recommend using one of the 2 workarounds listed below:
When recording with Apple Health Workout App, be sure to NOT manually pause your activity. When your activity is imported, we will calculate your moving time based on the GPS data being recorded.
Alternatively, if you need to pause your activity while you're recording, you can record with the Strava Watch App. This article can provide you with more information on how you can set this up.
Hi Jane,
Thanks for the response. I’ve looked by through my runs and it seems it’s been happening since the end of March onwards on random runs. I hadn’t noticed though until this week when I knew I definitely had run quicker than the pace strava said.
I don’t pause at all during runs so can’t try the advice given. Strava just usually cuts out any stops in the moving time which is what it doesn’t seem to be doing. If that helps.
Strange because other friends with the same phone and watch aren’t having the same issue.
Is there anything else can be tried?
many thanks
I can add I have the same issue. Just picked up a apple watch and wondered why the moving time is equal to the Elapsed Time. It's strange as the splits do show correctly with the periods of stops (at lights) removed.
Hello Jane,
a short update. when i sync a cycling workout, logged with the apple workout app, the moving time is calculated correct. with a running workout still problems
I am having the same issue. Mode: running and it happens when I pause the run manually!
Hi Jane,
all of a sudden have the same issue. Worked all fine until Monday. Same watch and phone since April.
I’ve tried every GPS reset and location services reset and all sorts. No luck. I have NEVER manually paused any workout.
it’s like Strava or Apple suddenly can’t see the stationary time. What is even more weird is that the splits and segments are still accurately recorded and match my fellow runners but the average pace is just reflected as weird.
I agree with others- it’s very hard to train speed work or long distance if you don’t really know how fast one is running.
Yeah that’s exactly the same issue. Was working totally fine now something is not recognising any stops in my run. Still not resolved and was basically told it’s a bug they’re working on. So nothing can be done.
Mine was also doing this (I replied in this thread elsewhere) but has started working (my moving and elapsed are now different) over the last week. I've never paused a run or walk. Not sure why but hopefully it continues to do so.
hello @Jane11
do you have some new information for this bug. In a month my training for the next marathon starts. It would be nice to see the correct times. (as it was last year)
i like strava because of the integration with apple, but after 1/2 year not working im starting to worry
many thanks in advanced,
jeroen
Even when I don’t pause a workout, the wrong amount of moving time shows up in Strava. It’s correct on my Apple Watch, but I’m Strava it’s much lower than what it actually is.
moving time and total time are the same. previous stopping for a trafic light was removed. this is not working now.
it works fine when i sync a cycling activity. but for running it is still not working
many thanks in advanced
jeroen
This is still not working and it’s been months. To clarify, I run with Apple Watch. I do not manually pause or auto-pause on Apple Watch, but I do stop to cross the road etc.
In the past Strava was able to analyse my run data when it was imported from the Health app, and adjust moving time accordingly.
As is the case for others in this thread, this is no longer working and there is no viable workaround meaning historic data is no longer directly comparable.
Is this an identified bug and is there a plan to fix it?
Same problem here. My elapsed time and moving time are identical, in the past the moving time was my actual moving time as the uploaded from the Apple Watch to Strava would calculate out any time stopped.
It happens the same to me. Even in workouts without pauses. Total time is the same as in apple, but the moving time is lower than apple, and no pauses were done.
Any update on this? It's almost a year in and the problem persists.
Thanks
I think it is working. i just checked strava and i can see a difference between moving time and total time 🙂
I've been experiencing the same issue with both my AW series 6 and hope it's resolved soon.
While being in contact with the developer of WorkOutDoors (a must have app for Apple Watch runners), he explained that the problem is related to how Strava interprets FIT files used to import workouts. A FIT file has a record for every second, and having two or more records with the same GPS coordinates is interpreted by Strava as if the user is not moving at all for one or more seconds. Unfortunately, this can happen because the watch struggles to get updated GPS coordinates and ends up recording the same coordinates in two subsequent records.
I’ve opened a ticket with Strava Support recently, trying to explain the issue, but they simply refuse to listen/understand.
For WorkOutDoors users, the issue can be easily resolved by switching distance & pace source from Apple to GPS: This will prevent having 2 records with same coordinates. Hope it helps.
