On a ride last week I had a strange problem where the elevation was being shown for the wrong location, lagging behind where I actually was. it got progressively worse and by the end of the 100k ride was behind by about 500m. I was getting climbpro notifications of upcoming climbs, when I was already half way through them.
I've seen this once before, when I was doing the Dragon ride a few years ago, and wonder if anyone else has seen it?
My 1040 is on the beta programme, but I confirmed that other people in the group using Garmin devices (530 etc) and not on the beta had the same issue.
The ride was created on Strava and automatically transferred to Garmin Connect. As far as I can tell the route itself looks OK, and I create all my rides this way. I have 200+ routes created in my Strava account and use different ones weekly.
Looks similar to this issue
https://forums.garmin.com/sports-fitness/cycling/f/edge-830/294438/climb-pro-out-of-sync
There used to be an issue in the route transfer interface between Strava and Garmin, where the elevation data was completely messed up, could this be related?