# Previous Oauth Token is no more working **URL:** \ **Category:** Users and Groups\ **Tags:** api, server-to-server, s2s-oauth\ **Created:** [April 11, 2023, 8:42pm UTC](https://devforum.zoom.us/t/previous-oauth-token-is-no-more-working/86503 "2023-04-11T20:42:11Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![david5](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david5/32/40553_2.png) [@david5](https://devforum.zoom.us/u/david5)\ **Post date:** [April 19, 2023, 2:02pm UTC](https://devforum.zoom.us/t/previous-oauth-token-is-no-more-working/86503/3 "2023-04-19T14:02:05Z")
Unfortunately, the Server to Server OAuth app isn’t really set up for multiple environments nor clustered services. You have to ask Zoom for an increase to your index count and build your own token rotation system. 😢 > [@Randomly receiving "Invalid access token" for Server-to-Server OAuth](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432): > > Starting this week, we have started receiving a lot of errors when calling Zoom APIs with our Server-to-Server OAuth token. { "code": 124, "message": Invalid access token." } When I look at the access token in question, it has not expired…there’s plenty of time left. We also have logic in place to refresh the token well before it’s scheduled to expire. Has something changed about the way Server-to-Server OAuth access tokens are managed on the Zoom side? We’ve had to put in a retry mechanism… --- _[View the full topic](https://devforum.zoom.us/t/previous-oauth-token-is-no-more-working/86503)._