Error when getting Heart Rate Intraday

[Kuchiki]

We're getting following errors when querying the heart rate Intraday data of our customers:

Not Found

endpoint: "/1/user/-/activities/heart/date/[date]/1d/15m.json"
client id: "238X37", "238WTM", "238WDK", "238WSQ"

This error occurred every day at 22:00 from October 5, 2023 to October 10, 2023 trying to retrieve yesterday's data.
But at 21:15 on October 9, 2023 this error did not occur and we successfully retrieved the data.
Please investigate this error.

[Gordon-C]

Hi @Kuchiki 

I checked those 4 client IDs and neither of them have Intraday enabled.   I did see each application has a different user id.  Unless you have each application set to the "personal" application type, the intraday endpoint you are calling should error.   Based on the registered application information, it would be best to have a single application that queries the data for all 4 users.   

I'm not familiar with that error message.   Typically there would be more data returned.   If you call the same endpoints now using the dates between Oct 5 - 10, do you receive the data or the error "Not Found"?

Gordon

[Kuchiki]

I checked those 4 client IDs and neither of them have Intraday enabled. I did see each application has a different user id. Unless you have each application set to the "personal" application type, the intraday endpoint you are calling should error. Based on the registered application information, it would be best to have a single application that queries the data for all 4 users.

It may be best to query in one application, but since the batch is already running, I don't plan on changing it.
The problem is that to this day, the 22:00 batch continues to fail every day.
In order to isolate the cause, I added a batch that runs at 21:00 every day from October 10th to 18th, and it succeeded in querying data (the data acquisition target and code were not changed at all)
Why does the batch at 22:00 fail to query, but the batch at 21:00 succeeds?

I'm not familiar with that error message.   Typically there would be more data returned.

I am running the Fitbit API using a Python library.
When an error occurs during API execution, the error is handled within the library, so the detailed error is not known.
Reading the library's exception handling branch, I'm pretty sure getting a 404 error.