Water logging history is in ounces

[ocrose61]

Is the water logging feature going to be fixed? I have logged 64 ounces of water daily for years and now it shows two ounces daily for years. At this point, I’m actively shopping for a new device and platform. This is very disappointing. I’ve also had steps disappear as I’m walking.

Moderator Edit: Clarified subject and word choice

[LizzyFitbit]

Hi there, @ocrose61.

Thanks for bringing this to my attention. I wanted to let you know that this issue with the water intake history showing in ounces was escalated to our team and they're working hard to get it fixed.

I understand where you're coming from and apologize for this inconvenience this has caused. Please know we'll share more information as soon as it becomes available.

[ocrose61]

Thank you. I have almost always logged water using MyFitnessPal since they are linked and that is no longer logging accurately. Eight ounces logged in MyFitnessPal comes out a fraction of that in Fitbit so it’s no longer accurate that way. 

[LizzyFitbit]

@ocrose61 It's good to see you around.

You're welcome, and thanks for the additional information. I understand you're experiencing some trouble with the data being logged on MyFitnessPal. It seems this issue is affecting the water tracking tile, and other related features.

Please know that our team is actively working on resolving this, and we'll definitely keep you informed once we receive more information.

[Allie-L]

Did they ever make progress on this?? I have the same issue, and my data never came back!

[LizzyFitbit]

Hi there, @Allie-L.

Thanks for joining this thread. I want to let you know that our team continues working hard to bring a fix for all our members. I'm sorry for this inconvenience and rest assured that I'll update this thread as soon as I receive more information.

[LizzyFitbit · Accepted solution]

Hi there, @ocrose61 and @Allie-L.

I have great news to share. A fix for this issue regarding your historical data showing up in ounces is coming in our next app release. The Fitbit app 4.43 is slowly rolling-out to all our members, so please install it as soon as you see it available in the App store.

Once again, thanks for your patience throughout this process. Keep me posted on the outcome.

[ocrose61]

Thank you!  It works now. I really appreciate it. 

[LizzyFitbit]

@ocrose61 It's great to see you around.

That's awesome news! I'm glad your water logs are displayed correctly on the Fitbit app and thank you for keeping us posted. I hope you can keep working toward your goals.

Have a good one!

[Gal221]

Lizzy Fitbit, hi. I found this thread because my app was updated today to 4.43, and my water history is now showing thousands of ounces per day, in the past. Thousands! 
Please help! 

[ocrose61]

Mine did the same thing. I just left it. Since the update though, all the logging has been correct. The dates from when the hiccup occurred until the fix now show something like 1298 ounces a day instead of 64. 

[Gal221]

Hopefully mine will get corrected at some point. 

[LizzyFitbit]

Hi there, @ocrose61. @Gal221 Welcome to the community.

Thanks for sharing this information with me. I'd like to share with you that our team is working hard to investigate how to resolve the incorrect water logs that were logged using App releases 4.39 to 4.42.

With this in mind and because it's been a few days, could you confirm if you continue experiencing inflated historical water logs since upgrading to app release 4.43? Let me know so I can keep our team informed of this situation.

[Gal221]

LizzyFitbit, hi. On May 21, my water log began showing the hugely large and incorrect water ounces, for that date and all logs prior in my history. 
Starting on May 22, the water logs for that date and since are correct. The history still shows thousands of ounces per day though for dates May 21 and prior. 
Thanks for working on this! Let me know if you want any more info or screenshots. 

[Allie-L]

Mine is doing the same thing, with massively high numbers listed for any day I logged water during the glitch!