Critical Sync Bug: Resetting secondary device overwrites Primary Wearable HR zones without warning

Hello Garmin Support Team,

I am writing to report a serious software bug regarding the synchronization of User Profile settings across multiple devices in Garmin Connect.

I own two devices: an Epix Pro (Gen 2) and a Fenix 5 Plus. The Epix Pro is configured and active as my Primary Wearable.

Yesterday, I performed a factory reset on my Fenix 5 Plus and re-paired it with the Garmin Connect app. Today, during my scheduled run, I discovered that this reset severely corrupted my user profile. The Garmin Connect app automatically pushed the default factory HR zones (based on the generic 220-age formula) from the newly reset Fenix 5 Plus directly to my Epix Pro, completely overwriting my customized Lactate Threshold (LTHR) zones.

As a result, my primary device (Epix Pro) displayed completely incorrect heart rate zones during my entire 1-hour workout. It registered a steady Zone 2 recovery run as a high-intensity Zone 4/Zone 5 threshold workout.

This bug caused severe issues:

Safety/Health Hazard: I was forced to guess my actual training zones during a high-heat workout, which caused unnecessary stress and elevated heart rate.

Data Corruption: My Training Load, EPOC, Recovery Time (which spiked to an absurd 44 hours), and Training Status metrics on my Primary Wearable are now completely ruined for the upcoming week.

A factory reset on a secondary, inactive device should never have the permission to silently overwrite the master user profile of the designated Primary Wearable. The cloud profile should sync down to the reset device, not vice versa.

Please forward this bug report to your software engineering and QA teams. Additionally, since Garmin Connect does not allow manual recalculation of Training Effect and HR zones for an already saved activity, please advise if there is any server-side way to force a re-evaluation of my latest activity based on my correct LTHR zones (183 bpm / Zone 2: 144-161 bpm).

I look forward to your prompt response and a resolution to this syncing behavior.

Best regards