You’ll want to implement your own key rotation strategy. I’ve outlined a proposed two-key rotation strategy if you have a shared database that relies on exactly one process succeeding on an UPDATE / WHERE statement matching the original renewal time, but if you anticipate long periods of inactivity, you’ll additionally need to decide what the others should do while the winner is renewing the access token — maybe reschedule your process to rerun in a minute.
I recommend creating duplicate applications for however many concurrent tokens you need, but others have had success with asking Zoom Developer Support to increase the number of tokens per application.