# Refresh Token Validity **URL:** \ **Category:** App Marketplace\ **Created:** [April 8, 2020, 9:52am UTC](https://devforum.zoom.us/t/refresh-token-validity/12093 "2020-04-08T09:52:23Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [April 8, 2020, 5:00pm UTC](https://devforum.zoom.us/t/refresh-token-validity/12093/2 "2020-04-08T17:00:49Z")
Hey @hedaoo.abhishek1993, Checkout these threads: > [@How to protect against losing refresh\_token response](https://devforum.zoom.us/t/how-to-protect-against-losing-refresh-token-response/10375): > > Description refresh\_token may be lost by the network Error The Zoom OAuth2 documentation [https://marketplace.zoom.us/docs/guides/auth/oauth#refreshing](https://marketplace.zoom.us/docs/guides/auth/oauth#refreshing) says “The latest refresh token must always be used for the next refresh request.” This way, if we make a request to get a new access token, and the request is successfully received by Zoom, and new tokens are issued, but on the way back there is a network failure, we would lose the new refresh token and the integration would no longer functio… > [@How to refresh token if refresh\_token in incorrect](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/19): > > Actually, it has happened again. And this time, I got to the diagnostic logs early enough to see why. Here is what happened: Client (my) code sends request with good OAuth refresh token, client ID and client secret to the Zoom OAuth server. Zoom OAuth server appears to have processed the request successfully, and is sending a response back with the new OAuth token. But, my client code got a gateway timeout exception reading the response. So, I never got the new OAuth token and thus now only… Thanks, Tommy --- _[View the full topic](https://devforum.zoom.us/t/refresh-token-validity/12093)._