Charge 6 not syncing menstruation from app

[Madi_52]

I just recently got my Charge 6 and everything is working great except for the menstruation portion of it. I’ve been tracking my period on Fitbit for years and the app clearly displays predictions to a tee but when I look on my Charge 6, it will have a random number that’s no where near what the app says.

I’ve tried: 

-manually syncing

-disconnecting from Bluetooth, force shutting Fitbit app, restarting charge 6, reopening the app and force a sync

-restarting both the charge 6 and my phone

Most of these attempts being multiple times. After becoming frustrated I then decided to just want the menstruation portion off the charge 6 if it’s not going to give me accurate information, only to find that I can’t do that without deleting it from Fitbit entirely which is equally as frustrating. I should either be able to have accurate information on the watch or not have to see it at all but neither seem to be an option here. Does anyone know how to fix this it?

[Sadavocados]

So I have been digging in to this myself because I have experienced the exact same thing, apparently it seems it is a very very common theme. Which irritates me to no end, not because of the issue itself necessarily, but because of this company's very apparent lack of trying. Which makes it evident that women* just do not matter to them as a demographic at all. In my digging I have seen lots of other women venting about this same issue, taking the same steps to try to resolve it on their own. No avail of course. But when I saw that a moderator did see some of the women's comments (who btw were from earlier 2024, they marked it as "Moderator edit: Clarified subject."  I'm holding on to some hope that they resolve this issue for all of us, because I am disappointed with them over their lack of effort. However, besides this defect, I do enjoy the product otherwise. 

[Madi_52]

Honestly that’s why I made this post because I also saw all the other posts about it, to show that it’s still a continuous issue on top of reporting it to support to no avail. It’s disappointing to see the lack of effort in trying to solve an issue that’s clearly been around for years.

[Russellgirl99]

I actually contacted support about this issue, hoping it would be an easier way to get a reply since this is an existing feature. I received an email not too long ago stating that they have addressed this bug in the next update they are rolling out. Hopefully this is true and the update will fix this issue. If it doesn't, I suggest reaching out to support through the chat or email feature. Existing features, I believe, don't have to go through the community vote/comment process to get attention... But, I don't know. Like I said, I'm hoping what I was told in the email is true and once the update is fully rolled out, it will be fixed...

[Esteine05]

So good to hear this! I've been having the same issue! I've rebooted, unpaired uninstalled. done everything I can and still no avail.