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

Experiencing undocumented error from the Activity Tracker api

On September 7th, around around 5:30pm (Eastern Time), we started getting an undocumented error from the Activity Tracker api:

 

https://api.fitbit.com/1/user/-/activities/tracker/steps/date/today/30d.json

Error message:

 

{"errors":[{"errorType":"system","fieldName":"n/a","message":"Not Found"}],"success":false}

Our jobs are scheduled to run every 15 minutes. According to our data, around 20% of the requests are failing. Most of the times, simply running the job manually solves the problem. But it's been more than 20 hours now and we are still experiencing the errors. The FitBit API Status page (https://status.fitbit.com/) doesn't show any recent incidents related to this problem, nor could I find similar issues on the Web API support forum.

 

We haven't updated this particular code in more than a month, and it's been working successfully for a long time and for the majority of the requests in the past 20 hours.

 

Looking forward to getting this issue solved. I'm more than happy to provide more info if necessary.

Best Answer
0 Votes
5 REPLIES 5

@gguerini: Are you still seeing this error?

Best Answer
0 Votes

Hi Jeremiah,

 

Yes, we are still seeing the error:

 

New Relic

 

Do you have any idea why this is happening? 

Best Answer
0 Votes

We have more info to share:

 

The error reported above seems to be resolved because we are not experiencing that anymore. But there's a new problem now:

 

When we POST https://api.fitbit.com/oauth2/token, we get a 404 Not Found response with the headers: 

 

{"Date"=>"Fri, 09 Sep 2016 15:25:07 GMT", "Content-Type"=>"text/plain", "Content-Length"=>"9", "Connection"=>"close", "X-Gateway-Error"=>"BACKEND_ROUTE_UNAVAILABLE", "X-Frame-Options"=>"SAMEORIGIN", "Server"=>"cloudflare-nginx", "CF-RAY"=>"2dfba6a5fde55723-IAD"}

It's strikes me to see this in the header:

 

X-Gateway-Error"=>"BACKEND_ROUTE_UNAVAILABLE"

 

 

Best Answer
0 Votes

This is what we are getting now:

 

OAuth2::Error: {"errors":[{"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: **************"}],"success":false}
Best Answer
0 Votes

@gguerini please contact us privately through the form here. If this is occuring for specific users, please include the affected user IDs in the form you send.

 

Runscope may also be of use for troubleshooting. You can use a standard account.

Best Answer
0 Votes