Connect IQ Datascreens reset after any kind of change to watchface etc

even with every sync of the watch with the connect iq ios app the datafields get erased and replaced with the timer data field.

unusable

I tried many things, even hardreset... still the connect IQ data fields get replaced by the Timer for whatever reason way to often. It is a joke

Can at least anybody here either confirm the same is happening to you, or let me know if this problem is not the case on your watch. 

is there really no FR55 user on these boards who is reading into this able to tell me, if their custom Connect IQ data fields get constantly erased or, if they do not have this problem at all? 

Is that what is happening to me? forums.garmin.com/.../ciq-data-fields-often-replaced-by-a-default-data-field

yes, same thing.

All IQ app developers I contacted told me it is a Garmin firmware problem. Garmin now replied it is a problem of the respecitve app.

now I tend to believe it is a firmware thing because not a single IQ app is excepted from this behaviour so far. 

Garmin tells me this is a problem created by the individual IQ app and I shall contact the respective developers.

BS - how is it possible that every (!) single datafield abd watchface I download from the IQ Store, even those created by Garmin :) do disappear for no reason once in a while abd are replace by stock datafields anf watchfaces.

This is a joke. 

Hello! Are you able to capture this on video and upload it here?

Garmin-Isabella

thanks for finally being active on this. Sorry, but this does not work. Just imagine, that you put an IQ datafield in your lets say RUN app, it is there, working, and at some point, the same day, a day later, whenever, after a sync with the Connect App or when changing something in the Setup of the watch .... it just disappeares, is exchanged by the Timer datafield and needs to be setup again... randomly 

That is about it. I cant capture that - it happens randomly, mostl after changing the watchface, sometimes after syncing or whenever.

Aye. It's not something any of us can video in any practical sense. I don't think the issue is being understood, given this request for video evidence :-(