Massive Fitbit Access Token/Refresh Failure

[kevinq21]

HI,

Was there any downtime for the Fitbit Web API that could have caused a massive access token/refresh failure? We do use the standard OAuth 2 flow. We have an intermediate service that allows us to grab data from multiple wearable services. For our other wearables, there was no disconnections  from other wearables. However, Fitbit we had about 80% of our users come back with a 500 error saying that the token was expired and we need to do a manual reconnect.

Thanks,
Kevin

[Gordon-C]

Hi @kevinq21 

I'm not aware of an outage.  If you received a 500 then your refresh tokens should not be out of sync and you just need to re-execute the refresh token request.   A 400 error, https://dev.fitbit.com/build/reference/web-api/troubleshooting-guide/error-messages/#400-bad-request... could be a refresh token issue.

Would you please private message me your client ID and the time frame of the 500 errors that you received?   I'll look into the problem more.

Gordon