Increase index size to solve “Invalid access token” for Server-to-Server OAuth

API Endpoint(s) and/or Zoom API Event(s)
AppId: Will be shared in personal message

New zoom token request invalidate the old one, and “Invalid access token” is being returned
We have an application running with 8 instances, Referring to this thread the solution should be increasing our app index size to specific number to be able to request more that zoom token and avoid invalidating the old token.

should we pass the current index? Actually we challenging configuring the app instances to expose index value, If we increased the app size to 8, Is there a way to call the Oauth api without passing token_index?

Is there a way to get the current allocated index using the zoom APIs?

Right now, we are using the zoom account in the production to generate the zoom token, Is there any affect on the current zoom auth request? Or the index will be defaulted to 0 if it is not passed?

{ "code": 124, "message": Invalid access token." }

How To Reproduce
Steps to reproduce the behavior:
*1. Request zoom token auth for the same user.
*2. Request zoom service with the old token,
*3. “code”: 124, “message”: Invalid access token." is being returned.

Hi @laith.maali if you do not pass the token_index value, it will be defaulted to 0