11-08-2020
04:05
- last edited on
12-14-2022
16:17
by
MatthewFitbit
11-08-2020
04:05
- last edited on
12-14-2022
16:17
by
MatthewFitbit
Whenever I try to delete Activity Zone Minutes from the Charge 4, I get this message saying "Something went wrong. Please try again later." There's always something wrong, or to quote Blackadder: "Something is always wrong, Balders. The fact that I am not a millionaire aristocrat with the sexual capacity of a rutting rhino is a constant niggle". I agree there with Blackadder but what annoys me more at the moment is that I cannot seem to delete Activity Zone Minutes from the Charge 4.
Any help?
Moderator Edit: Clarified subject
11-09-2020 05:52
11-09-2020 05:52
It's great to see you around, @RWJB.
Can you please be more specific about what you are trying to do? You want to delete your active zone minutes? Some screenshots would be great. In the meantime, check the article: What are Active Zone Minutes or active minutes on my Fitbit device?.
I hope to hear from you soon.
12-04-2020 22:42 - edited 12-04-2020 22:52
12-04-2020 22:42 - edited 12-04-2020 22:52
Same problem. Very frustrating, as it registered these when I wasn't wearing the device. Now can't delete.
03-21-2021 19:20
03-21-2021 19:20
Have there been any updates on how to fix this issue? I am having the exact same problem- the screenshot from Dani2281 is exactly what happens to me. I cannot delete any active minutes because that error always pops up.
04-21-2021 11:41
04-21-2021 11:41
Any news on this issue?
04-21-2021 11:44
04-21-2021 11:44
Nope. Mine now sometimes works and sometimes doesn't
06-29-2021 07:07
06-29-2021 07:07
I have this problem too. It gave me 61 active minutes in the middle of the night when I wasn't wearing my Versa 3 (I believe it is registering my window AC). I want to delete the minutes, but every time I try it says "Something went wrong. Please try again later." Well, it looks like this has been a known problem since at least November of last year, so how much "later" is it going to be before Fitbit fixes this??
07-02-2021 17:41
07-02-2021 17:41
Also happening here. Was really hoping some of this functionality wonkiness would improve after I got a Sense, but this is disappointing. Logged 1500 calories for me when I was only playing a game, so my stats for today are wrecked.
07-17-2021 08:31
07-17-2021 08:31
I made a memo of the times I wanted to delete, and tried again on various different days, and about 2 weeks later I suddenly was successful. Would be ideal if Fitbit would actually fix this, but just wanted to let people know that if you keep trying, it does seem possible to delete (sometimes).
01-12-2022 03:06
01-12-2022 03:06
Is there any update on this? It's been 2 years now and still an issue. I took my Fitbit off and it's clearly brushed up against something and logged 85 minutes erroneously. I need to delete them
03-06-2022 14:45
03-06-2022 14:45
Not sure if anyone will see this. I was having a similar problem and discovered that you can't just pick a large block of time to delete from the zone minutes. You have to specifically indicate the same times that the zone minutes are logged for. So if it says you got zone minutes between 4:00 and 4:13, you have to indicate that you want to delete the time between 4:00 and 4:13 or else you get the error. It's painfully specific to make work.
05-18-2022 11:52
05-18-2022 11:52
I tried this and is still didn't work. Crazy that for 2 years now they haven't fixed this. My heart rate monitor is the issue for me. It's always wrong and now it caused this activity and my calories are all off for MyFitnessPal.
02-19-2023 13:03
02-19-2023 13:03
So this is the bug, I think, and the work around. From my poking and prodding, it seems that the error occurs (for me, at least) when I try to delete the zone minutes for a specific period of time on one day. The app crashes, or you get the error ANY time the end date and time are BEFORE the start date and time.
When you start in the Delete AZM window, the default date and time values are:
What I noticed is that I can set the start date and time, with no problem - e.g. 27 DEC 2022 @ 7:30 PM
The error now occurs when I change the end date to 27 DEC 2022, because the end date & time are now BEFORE the start values.
If I change the end time FIRST, to 8:00 PM, and then change the date to 27 DEC 2022, there is no condition where the end date and time is before the start date and time, and I can delete the data.
I hope this makes sense.
CharlesKn | Mid-Atlantic, USA
60+, strength and cardio
Charge 5, Android, Windows