API 500 Errors

[InMemory]

We've started to receive a lot of API 500 errors beginning from around 18:30 UTC May 9th, this is an example: 

An error occurred with the Fitbit Web API while processing the request.Error id: 6CA2F53A:41BC_A92D826B:01BB_5912095B_1ACF5886:432B 

Nothing changed on our side since May 5th, so I'm guessing something's changed in the API? 

[SunsetRunner]

I am also experiencing the same issue. From 0 of these errors to many.

Example error response: [{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E2652:8679_A92D826B:01BB_59133757_3DA5DAAD:432E"}]

It started from at least  "May 9 18:27:49 2017 UTC".

Please help.

[AndrewFitbit]

Thanks for reporting this @SunsetRunner & @InMemory, I'll have someone take a look.

In the meantime, are you still getting 500s and if so how often? What requests are you making that result in 500s?

[InMemory]

The errors happen when requesting intraday time series, for example, for steps

GET /1/user/-/activities/steps/date/[date]/1min.json

[AndrewFitbit]

@InMemory Thanks.

Our team is working on a fix, thanks again for reporting @InMemory & @SunsetRunner

Edit: This should be fixed now.

http://www.fitbitstatus.com/

[SunsetRunner]

Thanks for the speedy response and the fix. However the issue has not been resolved for me. I still have many instances where this 500 error occurs (latest occurrence "May 10 20:54:56 2017 UTC").

Example: An error occurred with the Fitbit Web API while processing the request. Error id: A29E2652:2823_A92D91CB:01BB_59137DF7_DBB97F7:0B85 586a657d0380553900cdde38

Maybe your fix needs to propagate to all servers and this takes some time?

Update: The end point giving the error is: 

https://api.fitbit.com/1.2/user/user-id/sleep/date/startDate/endDate.json

[InMemory]

Thanks for the quick fix, the errors seem to have stopped 👍

[AndrewFitbit]

@SunsetRunner Hmm appears to be a separate, unrelated issue for that specific endpoint. The team is aware of it, I'm not sure of a timeline for a fix. Appreciate you calling this out, I'll likely update this thread if I hear anything.

[SunsetRunner]

@AndrewFitbit Thanks for the reply. Do you know when they will start the fix because I have many users that are not able to use my app?

[SunsetRunner]

I would have thought that the sleep API returning 500 errors when it shouldn't, would be a top priority for Fitbit. I have hundreds of users not able to sync sleep data and now my app is starting to receive bad reviews because of this issue. Is there a timescale for when this 500 error fix will be rolled out?

Many thanks

[SunsetRunner]

I have many instances where 500 error occurs (most recent occurrence "May 15 20:53:38 2017 UTC").

Example: An error occurred with the Fitbit Web API while processing the request. Error id: A29E2652:2823_A92D91CB:01BB_59137DF7_DBB97F7:0B85 586a657d0380553900cdde38

The end point giving the error seems to be: 

https://api.fitbit.com/1.2/user/user-id/sleep/date/startDate/endDate.json

This error is occurring hundreds of times per day for my app with users not able to sync sleep data and now my app is starting to receive bad reviews because of this issue. Is there a timescale for when this 500 error fix will be rolled out?

[AndrewFitbit]

@SunsetRunner The team is still investigating. I don't have any updates as far as a timeline for a fix.

[SunsetRunner]

I believe this could be affecting many other people apart from those using my application. Thank you for this update.

[SunsetRunner]

Please tell me the team has found and fixed the issue. As this is really causing me and I'm sure other people great issues.

We are still experiencing this error and all I can do is sit back and watch.

[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E2646:3914_A92D826B:01BB_5922A0AB_217B84A2:432C"}] 

[AndrewFitbit]

@SunsetRunner As far as I know, it's still scheduled to be worked on. I've also bumped it a few times already. 

Are you still using the Get Sleep Logs by Date Range endpoint? Would it be possible for you to use Get Sleep Logs by Date or Get Sleep Logs List instead? If you could you PM me some examples of user IDs + requests that you're making, that'd be helpful since I'm not able to reproduce the error on my end.

[SunsetRunner]

Thanks for the reply. I have already beein using the "Get Sleep Logs By Date" endpoint since it was updated to version "1.2": "'https://api.fitbit.com/1.2/user/[user-id]/sleep/date/[startDate]/[endDate].json'".

[JoshValidic]

Are there any updates on this? I am experiencing the same generic 500 errors when requesting sleep logs by date range.

[toristyner]

Also experiencing this error, need a fix!

[SunsetRunner]

Come on Fitbit really. This issue has been flagged for months and still not fixed. Now there are more 500 errors than ever before. I would have thought this was a major issue. Please, when will this be fixed and is there really any point in developing for Fitbit if major errors are never looked at?

[FedericoArg]

We are also experiencing this problem. Our current population base is 85K and we are getting 9K of this type of error each day.

Please include a fix for this problem.

Examples:

https://api.fitbit.com/1.2/user/-/sleep/date/2017-07-30/2017-08-30.json

Http Content: {"errors":[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: AC44412A:83FF_A92D826B:01BB_59A69DD0_5039F22E:6416"}],"success":false}

Http Content: {"errors":[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: AC44412A:741B_A92D826B:01BB_59A69D65_5038D83E:6416"}],"success":false}

Http Content: {"errors":[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: AC44412A:31A7_A92D826B:01BB_59A69D65_5038D910:6416"}],"success":false}

Http Content: {"errors":[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: AC44412A:7633_A92D91CB:01BB_59A69D3B_A44A2051:24CA"}],"success":false}