Intermittent 400 error when refreshing token "Save Access token into Database error"

Sometimes when we fetch a new access token, we get an error. This is a problem because access tokens only last 1 hour - so we need to fetch new tokens frequently.

We do use retries with exponential backoff, but sometimes we just can’t get a new token, despite retrying several times. This causes a lot of confusion for our customers, because Zoom appears to “not work” randomly for them, and then they blame our product.

I found this thread, but was hoping for more information or a way to stop these errors: Occasional error when refreshing access / zak tokens - #6 by tommy

We already refresh the token “on user action” rather than in bulk. We only refresh the token when the currently stored token has already expired.


{'reason': 'Invalid request : token created error: Save Access token into Database error', 'error': 'invalid_grant'}

Which App Type (OAuth / Chatbot / JWT / Webhook)?

Which Endpoint/s?

How To Reproduce (If applicable)
Not really applicable… we fetch a refresh token successfully using the same code hundreds of times per month.

Greetings, @basic,

Thank you for posting in the Zoom Developer forum. Aside from the aforementioned suggestion, can you share details on the things you’ve already tried implementing to reduce the number of errors? There are many best practice suggestions available on the internet but it’s ultimately your job to decide which solution is applicable to your situation. For instance, one approach you can consider is to set a scheduled job to refresh before the token expires. More details on this and alternative approaches can be found in this How to Refresh Access token effectively article.

I hope this helps,

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