Missing activity in log list but accessible via direct API call

[benedict42]

Hi, I'm experiencing an issue where a recorded activity does not appear in the Fitbit app or the Activity Log List API results after syncing, and I initially expected this to be a device issue.

However, the activity is accessible via the API when I reference its log ID directly. Specifically:

• The GET /1/user/-/activities/list.json?afterDate=2025-xx-xx&sort=asc&limit=95&offset=0 endpoint does not return this activity.

• When I try to create a manual activity via POST /1/user/-/activities.json for the same time, the response unexpectedly returns the missing recorded activity instead of the manual one.

• I can successfully access this activity using GET /1/user/-/activities/4568xxxxxxxxxxx6528.json (obfuscated due to content filter) , and its TCX file is also available.

This suggests a possible data integrity or API indexing issue.

Additionally, the activity data appears to be corrupt:

• Reported distance and duration are roughly half of what was recorded.

• The TCX data shows a single, fixed coordinate repeated throughout, even though speed, distance, and elevation values are logged per waypoint.

• On the map, it appears as though I barely moved.

I’ve seen the latter behaviour before. Sometimes, multiple TCX exports from the app seem to resolve it. But this time it persists.

It's a bicycle activity of about 6 hours, recorded via Fitbit on my Pixel Watch. The watch was in flight mode for battery savings while the recording finished, and the activity included a few pauses during the ride. This should still sync afterwards, so it doesn't explain the missing activity or the broken data returned by the API.

Has anyone else experienced something similar, or does Fitbit staff know what could cause this kind of behavior in the activity data or API indexing? I can provide additional details or logs if needed. Right now, both as a user and developer, this issue is quite frustrating.

[DorisFitbit]

Hi @benedict42 

Thanks for sharing your questions!

Problem/Solution #1:

Sometimes it takes a couple of syncs before all data is transferred to the Fitbit app.  If using GPS while recording an exercise, there is a lot of data (GPS coordinates) that need to be transferred. If the data is in the mobile app, then it should come from through the Web API. If the data is not appearing in the mobile app, then that might be a problem with the sync functionality (please me know). 

Problem/Solution #2: Corruption of data

Can Pixel Watch record GPS when in airplane mode?  The Pixel Watch can record GPS in airplane mode because GPS relies on satellite signals, not cellular or Wi-Fi connections. Airplane mode disables wireless radios to prevent interference, but you can re-enable Bluetooth and/or Wi-Fi while still in airplane mode to sync your data with the Fitbit app or use offline maps. 

How it works:

• GPS: The watch's built-in GPS uses satellite signals, which is a passive function that does not require a data or Wi-Fi connection.
• Airplane mode: This mode turns off all radios, including cellular, Wi-Fi, and sometimes Bluetooth.  I believe this also disabled LTE.
• To track: To track an activity like a run, you can use the on-board GPS while in airplane mode, but you'll need to manually re-enable Bluetooth or Wi-Fi to sync the data with the Fitbit app.

Missing GPS data could be the result of bad satellite connectivity.

• Bad satellite connection on a Pixel Watch is often caused by physical obstructions, improper positioning, or poor signal strength from your cellular carrier if you are connected to LTE. To improve connection, you need to ensure a clear line of sight to the sky, hold the watch steady, and be aware of your environment. For GPS-related issues, consider updating the Fitbit app, changing location settings, or restarting the watch.
• GPS signals can sometimes drop during activities. Try restarting the exercise app.
• Some users have reported that GPS and Bluetooth issues could be hardware-related.
• https://support.google.com/googlepixelwatch/answer/13579198?hl=en Did you turn off airplane mode before syncing?  This appears to be required.