Glances/Widgets

It doesn't normally happen when you perform a software update but we have seen an occasional report of certain settings needing to be reset back to where there were. I am sorry the update reset your glances.

That happens to me also, though I see it quite often after syncing using Garmin Connect via USB on my MacBook Pro. It also happened on my Fenix 6 so I don't think it's an issue with the watches but instead with the Garmin Connect servers sending the default widget config.

Garmin - Chris This just happened again to me this morning and there was no software update (though there was an update to the Connect IQ app). There is definitely something squirrelly going on. Is there something I can do to help figure this out? I only ever see this when connecting to Garmin Express on my MacBook Pro so perhaps you can check with that team?

Here is another such report: forums.garmin.com/.../glances-out-of-order-after-garmin-express-sync

Same on my Fenix 7x solor Sapphire titanium... Widget glances and watchfaces can be in a different order, or missing after a sync with Express....or update... 

Also express sees 38apps out of 33,and won't allow me to install anything because there's not enough room, when there actually is... Because of widgets, being changed to glance apps on the newer devices, and the store through Express not being implementing correctly with glance apps,counting them twice, because glances are now apps.

It happen to me after installed the latest beta (10.44) and then restarted device by first shut it down and then turn it on. After restart glances was reseted to default. Would be great if fixed since so annoying to reorganize the glances again when this happens

Same. 

For anyone following along, the Fenix 7 series official thread to report this happening is here: Glance Folders Disappear

My sincere apologies for the glances being reset randomly when syncing through a Mac computer and Garmin Express.

Garmin - Chris i sent you a pm!

I can confirm that I no longer see this issue on SW 11.21 (Beta). Maybe it was solved already in 10.44. Thus seems to have been fixed