Charge 3 SmartTrack isn't working

[TMatthes]

For the last 3 days, my Charge 3 isn’t recognizing my steps as exercise. I reset my Charge 3 multiple times, I’ve reset my phone multiple times as well. Any suggestions?

Thank you!

Moderator edit: subject for clarity

[AlejandraFitbit]

It's great to see you around, @TMatthes.

Thanks for troubleshooting this SmartTrack issue. By default, SmartTrack recognizes an exercise that lasts at least 15 minutes. If your activities aren't being recognized, lowering the time auto-exercise recognition setting to 10 minutes may help ensure they record properly.

For more information about how SmartTrack tracks activities, review our help article: Which activities does my Fitbit device track automatically?.

Let me know the outcome. 🙂

[Momcloud]

Still not working. I’m just going to manually enter my exercise. It worked
as normal till Monday. Lost my exercise for Monday- Wednesday had to go
back and add manually. No big deal, just more of a hassle and I’ll have to
remember to do it every time.

[AlejandraFitbit]

Good to see you here, @Momcloud.

I appreciate the information provided. This issue was escalated to our team and it should be solved by now. If you're still experiencing issues with SmartTrack, please restart your Charge 3 and try again.

Keep me posted. 

[Momcloud]

Still not working only works if I manually enter or use the part of app
with map and have to hit start and finish.

[Momcloud]

 This week added manually with last week exercise automatically  recognized.

[Momcloud]

As of yesterday afternoon my Fitbit is back to auto recognizing my daily exercise. Thanks for your patience and efforts to restore that function.

[AlejandraFitbit]

Thanks for the information and the screenshots, @Momcloud.

I am glad to hear that your Charge 3 is now working properly. If there is anything else we can help you with, do not hesitate to post it.

Happy stepping! 😉

[TMatthes]

It is NOT working properly!
Don’t assume it is....I never responded with anything suggesting it was fixed! It’s a continuing problem - period.
Thanks anyway

Sent from my iPhone