Recorded Elevation Issues

Internally the watch records ascent and descent in metres, regardless of the units on the watch or in Connect, so I don't think what you're saying is *literally* happening.

For any of metric that's saved by the watch to the activity FIT file: there's the fixed internal units [e.g. m/s for speed], the fixed units that are written to FIT file [usually same as the internal units], the user configurable display units on the watch (e.g. minutes per km for pace), and the user configurable display units in Connect.

For this reason, any choice of units on the watch or in Connect should not have an effect on what's recorded in the FIT file.

You can try to verify some of what I'm saying by opening an activity in the Connect website, clicking the gear icon (top-right of page) and clicking Export File. This will download the activity FIT file inside a ZIP file, which can be opened with the free https://www.fitfileviewer.com/ site. You will see that the literal units for things like speed, ascent and descent never change between FIT files, regardless of your user-configured display units.

B1nny said:

Looks like the watch is reporting ascent as Feet and passing this to Garmin Connect, even though format is set to Meters.

Do you mean that:

A) the watch records 30 m of actual ascent (for example) but displays 30 feet (or 9.144 metres) in Connect, meaning the actual magnitude is wrong? If so, how do you know the watch really recorded 30 m of actual ascent instead of recording ~9 metres of ascent due to some other factors?  In this case, does it happen consistently?

B) the watch records 30 m of actual ascent (for example) but displays ~9.1 feet, in which case the magnitude is correct, but the display units are wrong. In this case, I would say the fix would be to change your units in Connect (which are completely separate from the units on the watch, except in the special case of pool size, where the pool size units you select at the beginning of the activity determine the units that are displayed in Connect.)

In this case of A), I would suggest that even though ascent/descent may be reported incorrectly, it's probably just a coincidence that the recorded value is about 0.3 times the actual value (which makes it seem like the value was reported in feet when it should've been reported in metres).