[GCM BUG] Stress / Body Battery overnight history missing despite present on watch

Not a new bug in the app, but there seem to be a problem with the syncing of the data to the Garmin Connect account. Remove and Add a Device From the Garmin Connect App | Garmin Customer Support, then log a few minutes of steps and HR, and record a test activity, sync, and see whether it helped. If not, then have a look at the Troubleshooting guide for (some) data missing after syncing for more tips.

Hi, and thanks for your reply! 

Why do you think I'm just now experiencing this issue after many years with Garmin products without such occurence? I'm curious what could trigger such a problem with syncing the data from the watch to the GC environment.

This kind of problems may be caused for example by reinstalling the app, by changing the phone, or it can happen accidentally. Basically there is certainly no general bug in the app causing the missing data, since if it were the case, there would be thousands of people complaining here.

Thanks for the input! I'd be more interested in any other reason related to the Garmin environment why this might happen, (for example you mention that it happened 'by accident' - could you please elaborate this from a technical standpoint?) as my environment / set up has not changed. Same syncing behaviour, same phone, same watch, same GCM version, same activities, same sleep, same WiFi connection, I wear the watch on the same arm (I have not taken it off), etc. I have not changed anything on my side. 

Thank you! 

Adrian s said:

why this might happen

Typically it happens when the association of the device and the GC account is not unique. Usually (though not always) it happens when you change accounts, when the watch was previously associated with different account, when you accidentally create another account, etc.

Try the steps suggested in my initial post. If it helps, then the corrupted device-account association was indeed the culprit. If it does not help, there may be another problem with syncing. In that case you may find some clues if you browse through the Device Sync Audits (see it at the bottom of the app menu » Settings).

Thanks! I have only one account, have not created a new one (even by mistake), the watch was brand new when I started using it (not refurbed or second hand), I am the one who activated it, and has been associated with only my account from the beginning. I am also using the same (and only) phone as always, and I have the GCM app installed only on this one.

So that's why I highly doubt there might be any 'device-account association' issue, there's one mobile device, one watch, one account from the beginning.

Unless someone created a ghost account while I was asleep last night, in which case Garmin would have more serious issues to address :-)

I think it becomes clear why I'm reluctant to do any device disassociations or relogins on my account to fix a hypothetical situation which I might not be facing here.

Thanks anyway for your time and effort to provide the explanations and solutions. 

Adrian s said:

I think it becomes clear why I'm reluctant to do any device disassociations or relogins on my account to fix a hypothetical situation which I might not be facing here.

Well, in that case you can either wait that the issue fixes miraculously itself, or you can investigate the Sync Audits, or you can reach out to the Product Support. Though, they will likely suggest you the same thing, besides telling you to factory-reset your watch (which on my mind is not necessary). You can also downgrade to an older version of the app (find older versions at apkmirror.com), if you still suspect a bug in the app.

Honestly at this point it's irrelevant if this, now historical data, will be populated into GCM, as long as I have it on the watch it's all that matters to me. I'm not expecting a "miracle" to fix the issue, but I also believe there's nothing 'magic' in this technology as everything is man-made and supported by cold, hard science. As an IT&C Engineer with an active career, I understand how the system and the devices work, down to the most basic sensor on the motherboard in the watch, and I can also assess that I have not made ANY change that could have triggered this behavior in the day leading up to t he issue. 

What I do want to avoid is for it to happen again in the future. And if it doesn't, it proves my point that the aforementioned corrective actions were of no use in this situation. If it does continue to happen at random, in the absence of a duplicate setup or "ghost account", it can indicate that indeed a bug exists. Not necessarily in the app itself, but somewhere in the environment as a whole. 

I've filed a support request even before posting on the forum, and I'm ready to provide logs / files, to try to understand exactly what happened. The reason I created the post on the forum is to see if anyone else experienced the issue. I do agree we would have seen more traction on the forum, if it were the case, but I also acknowledge that this type of non-critical glitch wouldn't have a lot of people bothered enough to post on the forums, especially if it happened only once or twice in the lifecycle of their device. 

Thanks again for your time and patience and I appreciate your replies!

Adrian s said:

The reason I created the post on the forum is to see if anyone else experienced the issue.

Not me

Adrian s said:

Is this a new bug? 

No, it doesn't look like that's the case.

Thanks for your reply!