Missing Heart Rate Data from Some API Calls

[jcastle0]

I have an app that uses the following route to receive activity data including heart rate zone data: 

https://api.fitbit.com/1/user/-/activities/list.json

The app has been in use for several years and does have the scope required for the heart rate data. Starting around February 6, many of the activities returned by this route do not have the heart rate zone activity data included in the response. I can look at data pulled before 2/6 and see the activities with heart rate zone data, but now when I make the API calls the heart rate data on the exact same activities is missing. However, the problem does not affect all activities, as some do still return heart rate zone data. I cannot find any rhyme or reason as to which activities do or do not return the heart rate zone data.

Is this related to the service disruption on 2/6? If so, when might I expect the heart rate zone data to appear again on those activities?

[Gordon-C]

Hi @jcastle0 

I don't know if the disruption experienced this week had an impact to the heart rate zone data for the recorded exercise.   It's possible since the outage affected sync.   I would like to get some examples from you.   So, I will create a support case and email you to the address associated with your id.

If you don't see an email from me in a few minutes, please check your spam folder.

Best,

Gordon

[jcastle0]

Email received. I'll reply momentarily.