09-28-2020 12:53
09-28-2020 12:53
It appears about 3 hours ago we started to see 5xx errors ramp up. At this point, it's about 1 out of 4 requests for data are now receiving a 5xx error. Can Fitbit assist?
Examples of these errors are:
The remote server returned an error: (503) Server Unavailable.
The remote server returned an error: (504) Gateway Timeout.
{"errors":[{"errorType":"request","fieldName":"500","message":"Oops! An unexpected error occurred. If it continues please report it at help.fitbit.com. Error id: 024219fffe2ac82e-003c44f7-04b9539a-aea69cadd16c02f2-cc1da1e4-4"}],"success":false}
<html><head><meta http-equiv="content-type" content="text/html;charset=utf-8"><title>502 Server Error</title></head><body text=#000000 bgcolor=#ffffff><h1>Error: Server Error</h1><h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2><h2></h2></body></html>
09-30-2020 18:28
09-30-2020 18:28
Hi @jeaglemc,
Can you provide me with the endpoints you're calling that's returning 500s? Also, are you still encountering this issue?
10-01-2020 13:43 - edited 10-01-2020 13:43
10-01-2020 13:43 - edited 10-01-2020 13:43
Hello -
A lot better today. The concerning quantity of errors cleared up about an hour or two after my 09/28 post (I assumed somebody worked on it); there are only a few occurring today and only 503 - for example:
The remote server returned an error: (503) Server Unavailable.
At the quantity they're occurring now (about 0.15% of our calls -- quite a drop from 25% two days ago), I wouldn't report it. But if you do want to further investigate these few, we are calling:
http s://api.fitbit.com/1/user/-/activities/tracker/date/{date}/{1d or an end date}.json/{steps, distance, minutesFairlyActive, minutesVeryActive, activityCalories}
I hope that answer makes sense. Every now and then (again, about 0.15% of our calls -- quite a drop from about 25% two days ago) a variation of the above receives a 503.
Kind regards.
Jay