Are you saying that if I have multiple instances of my service running (as one would expect for a scalable, redundant application), that I can only have one valid access_token across all those instances? In other words, each time I call https://zoom.us/oauth/token?grant_type=account_credentials&account_id=[account id], it invalidates the previous access token that was issued?
If this is the case, how are we supposed to build a clustered application that makes API requests in the Server-to-Server OAuth case? I don’t really want to have to keep the access token in a single place and try to synchronize it across all the instances of my application.