Some settings and alarms being lost - please help!

I got my new Fenix 5X yesterday, an upgrade from my Fenix 3 Sapphire (not the HR version). I have done all the updates and started to customise some of the settings however I am finding that it is not remembering some of the settings and any of the alarms I set and I am finding that they are lost within an hour or so. So far the settings I have noticed that are not remembered are the sound settings for key tones, Alert tones and Key vibe. I have turned the watch off and restarted it but that makes no difference. I have found that it is sometimes (possibly always) caused when it syncs with Garmin Connect on my phone.

Can anyone help? I didn?t get this with the Fenix 3 and it is very frustrating especially the alarms!

Thanks.
  • Which settings?

    I have indeed found that the alarms issue has not been solved but everything else seems OK now... as far as I can tell

    I hope they get this sorted soon, it is so frustrating!

  • Any of the watch settings that are in the device settings on Garmin Connect, such as vibration and tone settings. Eventually Garmin Connect overwrites whatever device settings you might have set on the watch more recently; maybe not after first sync, but eventually it will happen. What certainly has never happened is a more recent setting on the watch overwriting what's in Garmin Connect; a 2 way sync. The units settings being overwritten was an aberration as the individual units settings are not even listed in Garmin Connect, so no option to even set things up in Garmin Connect as a workaround.
  • You're right! I tested those yesterday and they seemed OK but today they aren't :-(
  • I have the same problem. Manually written alarm gets overwritten by the GC app.I am shocked that such a major issue in a basic thing like setting an alarm is not resolved immediately. They sell these units at unbelievable rate and amounts yet unable to fine tune primitive task.
  • There's a post further up this page which points out that there are significant changes needed both to watch and to site back end to fix this. Your fauxtrage would be better directed at asking why they implemented it this way in the first place.