enum QuotaError.Reason (v202411)

  • QuotaError.Reason defines the reasons for exceeding the allowed quota for various Google Ad Manager services.

  • Exceeding the quota can occur due to high request rates, surpassing report job limits, or exceeding segment population upload limits.

  • Solutions include waiting and retrying requests with increased wait times or limiting the number of requests per hour.

  • The QuotaError.Reason enumeration includes specific values like EXCEEDED_QUOTA, REPORT_JOB_LIMIT, SEGMENT_POPULATION_LIMIT, and UNKNOWN.


Namespace
https://www.google.com/apis/ads/publisher/v202411
Enumeration Description
EXCEEDED_QUOTA The number of requests made per second is too high and has exceeded the allowable limit. The recommended approach to handle this error is to wait about 5 seconds and then retry the request. Note that this does not guarantee the request will succeed. If it fails again, try increasing the wait time.

Another way to mitigate this error is to limit requests to 8 per second for Ad Manager 360 accounts, or 2 per second for Ad Manager accounts. Once again this does not guarantee that every request will succeed, but may help reduce the number of times you receive this error.

UNKNOWN The value returned if the actual value is not exposed by the requested API version.
REPORT_JOB_LIMIT This user has exceeded the allowed number of new report requests per hour (this includes both reports run via the UI and reports run via ReportService.runReportJob). The recommended approach to handle this error is to wait about 10 minutes and then retry the request. Note that this does not guarantee the request will succeed. If it fails again, try increasing the wait time.

Another way to mitigate this error is to limit the number of new report requests to 250 per hour per user. Once again, this does not guarantee that every request will succeed, but may help reduce the number of times you receive this error.

SEGMENT_POPULATION_LIMIT This network has exceeded the allowed number of identifiers uploaded within a 24 hour period. The recommended approach to handle this error is to wait 30 minutes and then retry the request. Note that this does not guarantee the request will succeed. If it fails again, try increasing the wait time.