i have a question, reading on the documentation i found this:
The API limits the number of active access tokens associated with a given refresh token. The limit is 50 token per client/user (that is, a user can only have 50 tokens live at a time per client ID). If multiple threads sharing the same authorization were to simultaneously refresh, some of them might not have working credentials at the end of the refresh. Synchronizing on the refresh operation prevents the application from inadvertently overrunning its limit.
but it is unclear to me.
do api limit only the number of live access tokens or also the number of refresh tokens?
for example, if I have to manage 500 users, can I save 500 pairs of access tokens / refresh tokens and then update them (when necessary) synchronously? or risk of being unauthorized for some users?