Reaching or exceeding Google API quotas

Problem 

If you are experiencing errors such as "User Rate Limit Exceeded", you are reaching or exceeding your destination Google Gmail, Calendar or Drive account's API quota. These quotas usually reset after a 24 hour period, and migrations can be rerun / continued.

 

Solution

These errors are explained by Google here Google Drive API Handle Errors and here Gmail API Usage Limits and they offer some solutions such as increasing the API quotas (manually or by request) or applying "exponential backoff". CloudM Migrate already applies exponential backoff, but we have some other solutions available in the configuration:

  1. Maximum User Migrations: Reduce the number of users that are concurrently running.  This can be set in the CloudM Migrate Service Manager. 
  2. (If Google Drive) Reduce the Drive thread count: General Migration Settings > Advanced Settings > Other Options > Drive Thread Count (reducing from 3 to 2 will make a big difference)
  3. Implement a delay on the export of items from the source: General Migration Settings > Advanced Settings > Other Options > Item Export Delay

mceclip1.png

  1. 'Destination Platform Migration Settings' > G Suite / Google Workspace > 'Drive Options' > 'Batch permissions' is also an option, whereby CloudM Migrate will batch permission requests. This, however, is more error prone!

 mceclip2.png

Note: you can choose one or a combination / all of the above, but essentially, each reduces the speed of your migration and should work around the quotas in place by Google.

 

User Rate Limit Exceeded

Please bear in mind, that the "user rate limit" is not visible in your G Suite cloud console, however, the above troubleshooting steps 2 and 3 will still help in this regard.

For more information, see Google Drive API User Rate Limit Exceeded or contact Google directly.

 

Contact Google Directly

API Rate Limiting is implemented by Google, and not something that CloudM Migrate can control. If you are still experiencing rate-limiting, it's best to contact Google directly.

 

Was this article helpful?
0 out of 1 found this helpful