Lactate threshold pace different in Garmin Connect and watch?

Could it by any chance be related to GPS pace vs. footpod pace? (Ref previous data source discussions) I'm not sure what goes into the fit-files, but if both sets of pace data is included, could it be that LT pace somehow is recalculated based on the other source upon importing to GCM/GCM?
(On the other hand, if I'm onto something, it's strange that the recalculated values are not pushed back to the watch through PhysioTrueUp...)

My latest LT update was Nov 19., and the values are matching between my F5+ and GCM, but in my case as well I think the LT Pace is about 00:30min/km too slow on the watch. The other day I did a 10K in 55 mins without going all out, so I would assume my LT should be closer to 06:00 (or even lower), rather than the current 06:36 estimate.

When I come to think about it, it's rather strange that I haven't had any LT updates after F6.0 was pushed out...

Good call. However, when I look at the semi-raw data in Golden Cheetah, there is only one speed field.

I then had a look at distance vs. speed, and they match up perfectly (expectable since both came from the Stryd).

It might be that the distance or speed in the LT pace was derived from logged GPS coordinates in some way. I haven't checked how those would match up with the difference.

I have the same issue I use always footpod distance and speed . It means is not works with footpod only gps?