Active Calories Timeout

[syncsolver]

Why is the active calories time series request so much slower to return than all the others?

[SunsetRunner]

---

@syncsolver wrote:

Why is the active calories time series request so much slower to return than all the others?

---

Could you please provide the exact endpoint you are calling?

[syncsolver]

activities/activityCalories from https://wiki.fitbit.com/display/API/API-Get-Time-Series

All the other end points, such as activities/calories return much faster. Note: this is especially evident when the account has more than a year of history, and the period is set to max. I have also noticed that if it times out (taking longer than 30 seconds), and then I call it again immediately, the second call responds somewhat faster (for instance, maybe 15-20 seconds).

[syncsolver]

Any update on this issue?

[syncsolver]

Hello?

[syncsolver]

Is anyone ever going to look into this bug? It seems to be getting worse and worse.

[JeremiahFitbit · Accepted solution]

Thank you for reporting the issue. I have forwarded this issue to the appropriate Fitbit engineering team. While we will address the issue, this is not a common use case and other issues currently have much higher prioritization.

[JeremiahFitbit]

@syncsolver : Please email api@fitbit.com with an example date range and user id where you were experiencing this problem. We'd like to benchmark a change that we're working on.

[JeremiahFitbit]

We've released a few performance optimizations on this endpoint. Thank you for the feedback.

[JonathanBloom]

This issue is still happening with Sync Solver.

[kaddison]

Yea, I just downloaded Sync Solver. All of my Fitbit data sync with Health app, minus my active calories. It's frustrating!

[AndrewFitbit]

@kaddison This thread/forum is about using the Fitbit Web API. If you have an issue with Sync Solver, you would need to contact them.