Hi everyone,
We are noticing an issue with running activities uploaded or synced via TCX files (specifically originating from Google Health / Fitbit) where Strava overrides the activity's total elapsed time and recalculates a significantly shorter moving time.
Upon sync/upload, Strava seems to ignore segments with manual pausing, resulting in a reduced moving duration while maintaining the full distance. This inflates the average pace drastically.
Do you have an idea, why the total time is miscalculated while syncing or uploading a running activity to Strava?
Best regards, Tobias Vossen
