did you try usinbg the list view and do a filter for Runs?
I am encountering the same problem and my settings for Elevation Correction have always been “No”, and GAP Model from Strava run.
My run is not flat, it contains laps on a hill. Runalyse and Suunto App, or the Suunto watch itself during the activity, show a totally different GAP (for each individual lap, and obviously as an average) than intervals.
Ah, I’m having the same problem with GAP in Intervals. No elevation correction, reprocessed. Just concerned that it affects the Load number as it determines Fitness line graph.
While in Runalyze, Pace & GAP are near identical as they should be since there’s almost no gradient.
Did you check the Settings page for these 2?
Elevation correction should be Yes or Auto in your case and the GAP model set to Strava Run.
Yep already did. I guess it’s proven to be my own Galaxy Watch issue so I literally ditched it, never used it again for workouts lol
I’m checking back in several months later with an update - I had previously (in Feb) changed my elevation correction to auto and that fixed things, but something has changed/broken since then. I have several examples but a recent one is showing up as 958ft climbed when Garmin and Strava websites show 179ft. I’ve changed the activity setting for elevation correction to ‘Yes’, even within the activity, and hit re-process, but it is reverting to 958ft (I had manually corrected it). This is causing a ridiculous GAP estimate. I also changed the global setting to ‘Yes’, and reprocessed this activity, but also to no avail.
Any ideas what I’m doing wrong?
Check your Elevation stream. Some devices log 0 elevation right after starting or when resuming after a pause. If you are at elevation, this immediately introduces large errors.
Fresh run this morning with new settings applied, altitude graph looks smooth, with no jumps. I can look at raw data if someone can recommend a process. Garmin/Strava report 230ft climbing, Intervals reports 530ft.
Same here. I had a run today where the elevation gain was 3-4x more than what’s reported by Garmin. My settings were GAP Model: Strava Run and Elevation Correction: Auto.
Problem first shows up for me 19 Sep 2025 (I don’t know if I changed the setting at that point or not), for the runs that were elevation corrected.
Yes, seems that something happened for me around that date as well. @MedTechCD should we cut a new bug ticket as it seems specific to a change deployed in September? I can look through release notes to try to find the issue.