As said in title, and shown in picture.
Off topic: I’m quite curious why Fitbit decided to use a inconsistent display(view)<—->algorithm&DB(model) mechanism(since I’m programmer too). It’s very buggy. A branch of small display bugs(resolved after a few times of re-launch the app or sync) I don’t have a screenshot. As a patch or quick fix will derived more hidden/unpredictable issues(that’s why we’re using the imperfect app now), you fundamentally need to rewrite the app(including backend infrastructure software) to completely solve problems.
Best Answer
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Hello @wilsonlmh, have a warm welcome to the Fitbit Community. 
I appreciate your participation in the Forums and for sharing your experience with us. I would also liek to thank you for including a screenshot in your post. At this moment, I have forwarded this information to our team so they can take a better look at this situation. Once we have more updates, we'll make sure to post them here in the official Forums.
Thanks for your patience and understanding, have a great day!
Best Answer
