No. Under the hood, we use the Personal Access Token of the user to make a request to Autodesk Identity. So using either set of credentials may (and I say
may because I am not sure exactly yet what is happening) result in hitting the same limits.
Every call to ShotGrid triggers a series of checks. And depending on the results, we will call Identity to get information about the user, obtain a new Autodesk Identity token, etc.)
Everyone one of these types of call has a rate limit.
The rate is global to all ShotGrid, and is per minutes.
The current situation is due to a bug on our side, which makes undesired additional calls and allows one script to over-consume the allowed budget. Thus impacting all of ShotGrid users.
This is obviously a situation that should not happen : one piece of rogue code somewhere should not impact all of ShotGrid users for all sites.
All of this must be implemented by us in a way that does not require clients to make changes to their code or take extra precautions. This should be done in a way transparent to API applications.
That being said, on the client side (meaning here your code), it is always a good network programming practice to throttle retries after an error condition (like this Quota limit exceeded). Using an initial random delay, and increasing the delay between re-attempt, to avoid all of your processes hitting the server again at the same time.
Immediately re-attempting the call is not a good practice.
But the TL:DR; version is : this error should not have occurred, and it is on us to fix. But there is a way for clients to not make the problem worse when it happens again (trying to be realistic, not pessimistic).