Refresh token no longer works after the API returned a 504

API and Webhooks
1

Hey,

Yesterday our app received a 504 gateway timeout while calling https://zoom.us/oauth/token to refresh a token. Now we get { "reason": "Invalid Token!", "error": "invalid_grant" } when we try use our stored refresh token.

First question: can we do anything, or have we lost that token and we need to ask the customer to re-authorize?

Second question: how do we stop this from happening again? Our app fetches data in the background and is mostly hands-off. Some customers never touch it again after authorizing. Asking them to authorize again apropos of nothing is annoying for both them and us. I’ve seen talk of increasing refresh token tolerance on this forum, but no details on what that does. Would that have helped?

Thanks,
Reece

2

Hi @reece.selwood
Thanks for reaching out to the Zoom Developer Forum, I am happy to help here!
Unfortunately when you lose your refresh token, the way to fix this is to ask the customer to reauthorize, we know this is not ideal and we are working on an alternate solution for this.

For your second question yes, that would have helped so you can store different tokens that work simultaneously

To enable this, feel free to reach out to our support team here:

3

This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.