Sense no longer generates stress management score

[rbeau18]

I have used my Sense daily for over two years but over the last three days my stress management score is no longer displaying. I only take my watch off to shower and charge so I basically wear it 23.5 hours a day. My sleep habits haven’t changed either. I tried a hard reset on the device and checked for both sense and app updates but my devices are both updated and the hard reset did nothing.  It’s strange how much I’ve come to rely on that score but it really gives me some meaningful information. Please help if you have also had this issue.

Moderator Edit: Clarified subject

[eezeepee]

@SuzyQ3 Actually, I don't think the stress score is even part of Fitbit Premium.

It's still not good that you're missing the information though.

[SuzyQ3]

My son doesn't have a premium account and he has no stress management score. He has the tile but no score so I am sure it is part of the premium features.

On the picture here below from my Fitbit app (in Dutch in my case) you can also see that the score is part of premium.

 

[jtchum62]

I deleted the Stress Management tile, then reinstalled it and now all my scores are back.

Sent from my iPhone

[eezeepee]

@SuzyQ3 You are correct.

Give the recommendation that @jtchum62 said. Hopefully it'll get it going again. 

[SuzyQ3]

I removed and reinstalled the tile several times yet, unfortunately it's not working for me. My score is not showing, except now, 2 weeks after it all started, the score from 8 until 16 February showed up suddenly. But I have no use for a score from two weeks ago, I would like the score for the day 😏 and why did it stop again because there was no update and I didn't change anything. 

[KSL86]

Still not working for me either, despite trying all the solutions multiple tines. It is both disheartening and irksome that Fitbit do not seem to care. Not sure I'll continue with premium if they don't take errors seriously. 

[Eyevy]

Hello. Just an update on the stress score. Had a few days that I had a score since 2/9. So that is interesting! Hopefully, fitbit will get it fixed soon. 

[Bradnag]

Same thing on my Charge 5. I meet all the criteria, and have tried all the recommended solutions. Looking around on the boards, I see other Charge 5 and Versa 3 users seeing the same symptoms. Fitbit is clinging to their "It's not us, it's you" line of support in all of ther forums I've read so far. So...yeah, this is fun.

[KSL86]

I've just upgraded my phone and am having the same issue on the new one. So it's definitely a problem Fitbit's end.

Like someone else above, the score initially stopped showing from the 10th, but now I have a retrospectively added score up to the 16th. But nothing since.

[eezeepee]

I think the issue is a server-side issue and not the Fitbit Sense itself. I get all my scores just fine and especially if it happens on other devices, it's gotta be on their end.

[SuzyQ3]

Because removing and reinstall the tile seems to solve the problem for some people, it has to be the Fitbit app or server that causes the problem not the devices. Strange that a few of our missing scores seem to appear after 2 weeks and then stop showing again. Today I had an update on the Fitbit app but so far no score, hope it will show up tomorrow 😏

[SuzyQ3]

The update yesterday unfortunately didn't fix the problem, again no score this morning 😞 

[LizzyFitbit]

Hi everyone.

Thanks for the continued reports and feedback about this situation. Our team is aware of this situation and they're currently working to bring a fix to all our affected members. I'm sorry you've had this experience and please know your feedback has been passed along to keep them informed of this situation. Once I have more details from our team, I'll update this thread.

As a side note, let me clarify that the stress management score is available to all our members that have a supported device such as the Sense. On the other hand, the detailed breakdown of your score will be displayed on the Fitbit app only if you have a Premium subscription. You can find more details about this here.

Once again, thanks for your patience and I'll update this thread as soon as I have more details from our team.

[sarcazm]

FYI - no patch with the last update.  

[eezeepee]

@sarcazm Update for iOS? There hasn't been one for Android since February 25, 2022.

[SuzyQ3]

I have an update on my Android Phone on March 1, 2022, but that didn't fix the problem. Hope Fitbit will find a solution soon, like LizzyFitbit promises 😊

[eezeepee]

@SuzyQ3 Hopefully. But like I've theorized, I think it's a server side issue. It at least something that's not app or hardware related. Either way, it needs to be fixed for those with the issue. 

[sarcazm]

Android, but the Feb 25 update (3.54.1) didn't come through for me until March 1.  

Sorry for the confusion.  Release date and OTA DL/Install dates are quite variable from person to person, so it makes more sense to go by date of availability for installation than date of release in the notes.  There might be people who don't even have it available yet, or don't set their Fitbit App to update automatically.  It wouldn't matter though if they finished it on date X but I couldn't put it on my phone until date X +n, and another person maybe date X +p.  

[sarcazm]

same date as i did.  so i tried the tile thing again (which is weird enough when you consider programming) and no dice.  

[sarcazm]

i agree.  i'm having multiple issues that started at the same time but they all seem to pull data from the same areas to provide different customer experiences on the front end of the apps and despite multiple tickets having been opened and some closed after escalation for weird fuzzy reasons like "your user experience may be different than others" i've gotten nowhere, and nobody wants to review my bug reports.  i've had people ask me to take screenshots of things that can't be screenshotted, using a Russell's teapot sort of philosophical argument to close my cases.  

so like many issues that are obvious errors in either the servers or in a bug fix/security update for something else that was a patch over the code below and caused deeper written code to poop the proverbial bed without realizing, perhaps, things were connected (which also happens really often in my personal experience).