Invalid refresh token

[MyWellportal]

Hi

On 14 Feb we got an invalid refresh token for more than 100 users. nothing changed in the code and it was working fine. We do save the new refresh token when we refresh it, but now we need to ask all users to sync again their devices and it's a lot. Is there any solution to restore the refresh tokens without asking users to sync again? Or can anyone see what happened?

Thanks

[JohnFitbit]

Hi @MyWellportal,

Welcome to the forums!

I'd like to take a closer look at your situation. Would you please submit a support case through our support form? Please be sure to include timestamps of when the issue occurred, and your client id. Thanks!

[MyWellportal]

Thank you John

I sent a support ticket # 00106798

Please can you see if you can help me with my request or ask all users to sync again which it's a bit hard? 

It's urgent, they have challenges running this month

Thanks

[PaulStDenis]

@JohnFitbit please post the responses to this forum to benefit the community instead of turning a thread into a private conversation.

on the Fitbit Web API authorization process.

I'm getting the following 3 different occasional responses from the server

system - n/a - Service Unavailable
Service Unavailable
Gateway Time-out

I believe that when these are from a refresh token request, the token becomes invalid. I've tried to retry these requests after a short timeout to resolve the issue but some user's tokens are still becoming invalid.

Is there a best practice for re-requesting a refresh token when the server responds with an error?

Is this caused by a rate limiting when my app is making requests or is the API server being overtaxed in general?