Not getting some movement reminders

[WUpdegrave]

I have restarted my Charge 5 and checked settings. Do not disturb is not on. I don't get my ten to eleven  AM movement reminder. Any help?

[janicekay63]

I have been having the same problem!

[RiekoC]

Hello @WUpdegrave & @janicekay63 

Every now & then, I won't get the reminder to move at 10 minutes to the hour. When this happens, I:

• Tap on the device icon in the upper left of the Fitbit app
• Tap on the Charge 5 tile
• Turn off Reminders to move under Settings
• Tap on the arrows in the upper right of the page to sync
• Turn Reminders to move back on
• Tap on the arrows in the upper right again to sync
• Restart the Charge 5 from the Settings tile on the device or by using the charging cable that came with your Fitbit

Usually, this is enough to get the Charge 5 "unstuck" and Reminders to move to work again.

BTW, I noticed that I didn't get a reminder to move in the afternoon although it was working in the morning. I did the process that I described above. So far, the reminders to move are working today. Hopefully, you will have the same success.

[Gumby51]

Tried this, didn't work. Any other suggestions?

[RiekoC]

Hello @Gumby51 

I don't have another suggestion to try. The process I described has worked for me so far. That said, I have noticed that it can take more than 1 attempt to get the Charge 5 "unstuck". It might be worth trying the process at least 1 more time.

[Gumby51]

I have tried several more times with no positive results.  Still do not get the hourly reminders for steps, the notification when I reach 10,000 steps, or the watch face when I move my wrist.  I have to tap the Fitbit like I did with my old Charge 3. Quite frustrating.

[gdio53]

@Gumby51 

For the screen wake issue, try this:

From the main screen, swipe down to Screen Wake, it should be set to Auto.  If it says Manual, tap the screen to toggle the setting.

[Superficies]

These reminders have never been consistent for me. I honestly think the Charge 5 doesn't have sufficient memory to keep this feature active at all times. Or maybe mine is just buggy?