Manually added walk has wrong duration & gets deleted on refreshing the page

[KenGould]

Yesterday (Saturday) I did a combination walk/run.  I let the Fitbit Charge 6 auto-recognise the workout & it created two exercises for me - a walk & a run.  I wanted to log the activity as a single workout so I deleted the two automatically added exercises & manually added the walk (1 hr 20 mins).  After adding the exercise the Fitbit App gave me a duration of just 12 minutes?  It looks like it is not allowing me to add the exercise for the period when the two automatic workouts were recorded.  If I then manually edit the exercise to the correct start time & duration and then save it again, the duration remains at 12 minutes.  If I then return to the Today page I can see that there is an exercise for Saturday (albeit the wrong duration).  If I then refresh the page on the Fitbit app the exercise disappears!  I'm on the latest Fitbit app software for iPhone; firmware on Charge 6 is the latest.  I've force closed the app & restarted the phone, but the problem still persists.

Please can someone help me fix this issue?  Many thanks

[RiekoC]

Hello @KenGould 

There's been an on-going issue on the Fitbit side that affects our ability to edit/add workouts in the Fitbit app. The team is aware of the issue and has been working on fixing the problem. So far, I haven't seen any timeline for the fix.

For now, there's no troubleshooting that we can recommend since the issue is on the Fitbit side.

[KenGould]

OK, many thanks for replying.  Much appreciated 👍.  At least they are aware of the problem.

[RiekoC]

You're welcome @KenGould , although I wish I had better news.

Are you getting the weekly Fitbit progress email? If so, check it to see if it shows the correct number of workout days. I've seen users report that although the app doesn't show all their workouts, the progress email had the correct number of workout days. This indicates to me that your data was properly uploaded to your account on the Fitbit servers and there is likely some kind of syncing issue between the Fitbit server and the app.