Sense 2 app run dashboard data: rounds running time, pace inaccurate & elevation way off?

[chuck39]

As a runner and stat guy, I have had a problem with the differences in the Fitbit app vs the browser view for my runs. The app rounds the ‘duration’ to the minute while the browser used to give the exact total time by including seconds. The mile ‘pace’ was usually different when I compared the app to the browser, it appears a fraction of a mile is given the same weight as an actual full mile when averaging  for mile pace in the app. The app ‘elevation gain’ was consistently about 3 times the elevation gain shown in the browser view. None of these differences made sense to me, why would the app and browser not have had the same exact stats???? Now with just the app available my data is not accurate enough to compare with my previous running data. Is there any fix for this?

[SpottySB]

This is a basic failure with the fitbit app.  You don't have to be a stats nerd or crazy athlete to want your total run time and pace per mile (or pace per km) for an activity.  Casual warriors run 5ks all the time! 

The updated fitbit app no longer reports total time to the second for a run, and the problem identified by Chuck39 is second problem with the app.  Until today, I could get the complete information from my wathc by logging on to the fitbit.com/activities website.  That's inconvenient, but at least I could still use my Charge 5 for training.  Today Google eliminated the website.  The only source of activity information is the failed app.

Before November 2023, the older version of the fitbit app was more capable and accurate.  This is lazy work by the app developer, and it makes a very fine watch work much worse.