Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Increased 500 Bad Gateway responses

Hello API Team,

 

Noticing an increase over the last 18 hours or so of BadGateway 500 errors. Mostly these are to intraday data, most often to intraday steps. 

Example response:

{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit API while processing the request. Please contact api@fitbit.com for assistance. Please reference error id: A29EFFF4:8B82_A92D900A:01BB_5882536F_6E9C5049:5F8C","success":false}"

Immediate retries of the same call typically succeed though. Just reporting. Thanks.

--Aaron

Using Fitbits in Research? Check out Fitabase --www.fitabase.com
Best Answer
3 REPLIES 3

Hey @aarondcoleman, we'll look into it. Thanks.

Andrew | Community Moderator, Fitbit

What motivates you?

Best Answer
0 Votes

Hi Fitbit Team,

I'm having the same problem. After getting about 10 json files for step data this error message was raised.

Best Answer

Good Morning! Yes, we're still encountering these 500s as well, continuing over the weekend. It's a small percentage, most retries succeed, but we do have some instances now where 3 consecutive retries fail, which is our threshold for kicking these out of our queue. Retries an hour or more later then succeed. Let me know if sending/posting the errorIds helps.

 

Thanks,

--Aaron

Using Fitbits in Research? Check out Fitabase --www.fitabase.com
Best Answer
0 Votes