Daily Readiness late/not working

[Tashnz]

For the last week or so my daily readiness hasn't been showing up in the morning. It either shows up around midnight if I check then, or it will finally be available the next day (for the previous day). So it's always delayed by about twelve to twenty four hours. Which obviously is a waste of time and not helpful to see how my stats show my body's readiness state based on HRV, sleep etc.

Is anyone else having this issue? I have a Charge 6, there is no update that I can see. The app is up to date also. Any idea what I can do about this? 

[Tashnz]

Thanks. I just updated that app, hoping there would be a fix, but no such luck. Which is disappointing! 

---

Update just came out, but with no fix for this issue… not ideal. 

[JuanFitbit]

Hi everybody! Thank you for your messages and further efforts.  I'll inform our team that the steps tried didn't help. 

Our team is looking into this and will work on a solution. 
Hopefully this gets solved soon. 

I'll be updating the thread as soon as we receive further info

[Msiqueira]

I noticed that my spo2 hss stopped being registered since thursday not sure if there was an update but now instead of "being late" is not getting recorded at all on the pixel watch 4

[MsVmmmm]

Followed all those steps but it didn't fix the problem.

[TerryG64]

Now almost 2 weeks and still no solution. Frustrating that this is taking so long to fix.

[Chriszz]

Agreed. An update would be great 

[KC73]

Same here with a inspire 3- i thought my device was faulty.

Previously the readiness score came delayed. Starting from 9-12 Dec, there's no readiness score all.

[Tashnz]

Wouldn't the 'fix' be tested before the update was released haha? Surely your team has the tech skills to test fixes beforehand right? Here's hoping it's not much longer. 

[Tashnz]

Had an update for my Charge 6, and once I synced it, the problemwas  fixed. Not sure if it's the same for everyone else? 

[TerryG64]

I am the same. Problem fixed with update to Versa 4.

[JuanFitbit]

Hi everybody! Thank you for your messages and feedback. 

I'm glad to read that the issue was solved for some of you. 

For those who are still having the issue, please make sure that you don't have a pending firmware update for your Fitbit devices/Pixel Watches (a banner should show in the app )  and the Fitbit app is up to date. 

If the issue persists, please let us know the phone model and operating system version ( Pixel Phone 6 Android 12, iPhone 16 iOS 18.2, etc) 

[KC73]

Hi,

it's fixed now- i can see the score today.

Thank you!

[AristoR]

Still not working, samsung a73 android 16, pixel 4 watch. Fitbit app updated dec 2 version 4.58

[Quoll]

Not fixed.

Pixel 8, Android, Inspire 3. Fitbit app up to date. Newest firmware installed yesterday on Inspire 3.

Also, there is a longstanding issue with the SpO2 measurements having the same problem. This has been reported since several years now. I know what the issue is, but moderators somehow don't want to communicate it to the developers, or the developers don't want to solve it: the issue is related to your timezone, hence why you'll see more bug reports about it from Australia, or any timezone that is significantly positively offset from UTC. It'll wrongly use UTC 00:00 as the cut-off time between days, rather than the correct time that takes your timezone into account. Hence, if you sleep past 10 am, or 11 am (depending on the season and daylight savings time), you'll see the SpO2 measurement on the correct, current day. If you wake up before that (which most people do), you seemingly don't get a measurement for today, and it is instead added to yesterday. This might even overwrite yesterday's measurement if you woke up yesterday after 10/11 am (in Australia; or UTC 00:00 more generally).

Now if some moderator wants to stop copy-pasting the d@mned "reset your this and that, reinstall everything and switch it off an on again" playbook, and instead pass on this information to the developers, that would be greatly appreciated.

I have a PhD in computer science and engineering, if that helps. All the above descriptions about these bugs have been verified in reproducible tests.