05-06-2026 07:28
05-06-2026 07:28
I'm not sure where to report this. The Google Health API support page (https://developers.google.com/health/support) links to the Issue Tracker but uses a nonexistent component ID (1914241), so you can't actually file an issue.
This bug concerns data points for recorded running activities as returned through the "list data points" and "reconcile data points" Google Health v4 APIs.
A "structured run" activity (created through "Build a run" on the Fitbit app, then sent to a wearable for tracking) sometimes reports as a "RUNNING" data point (with distance & pace included) and sometimes reports as a "WORKOUT" data point (with no distance or pace included). When the data point is returned as a "WORKOUT", there is no way to tell it is a run and thus no way to get running-specific metrics (distance, pace, etc.).
It seems to be related to the date/time filtering in the data points API request. If the run data point is "too old" (specifically, more than 64 days before the upper limit of the date/time filter), it reports as a "WORKOUT" with missing run data, otherwise it reports as "RUNNING" with full data.
See the following Gist: https://gist.github.com/josh2112/6b2e44b46f7c3958e1f875880edd5719
These results are from my personal Fitbit account. Each contain a query and a particular data point from the query response. In "correct.txt", the exercise type is "RUNNING", and all the expected running metrics are included. In "incorrect.txt", the date/time filter is one day later such that the offending data point is 65 days before the filter upper limit instead of 64 (data point is from March 1 2026, data point filter < May 5 2026). You can verify from the data point name and start time that both files contain the exact same data point, but now the exercise type is "WORKOUT", and important running metrics (like distanceMillimeters, averagePaceSecondsPerMeter, elevationGainMillimeters, avgCadenceStepsPerMinute, etc.) are missing.
This bug needs to be fixed before the Fitbit API goes away or there will be no way to reliably and consistently download data about running activities.