AI-generated Key Takeaways
-
The QuotaError indicates a client-side error where a user has no remaining quota for an action.
-
This error can occur across various Ad Manager services due to exceeding request limits.
-
Possible reasons for the QuotaError include exceeding requests per second, exceeding the limit for new report requests per hour, or exceeding the number of identifiers uploaded within a 24-hour period for segment population.
-
Recommended approaches to handle QuotaErrors generally involve waiting and retrying the request, and potentially limiting the rate of future requests.
-
Specific wait times and request limits vary depending on the reason for the quota error and the type of Ad Manager account.
Describes a client-side error on which a user is attempting to perform an action to which they have no quota remaining.
- Namespace
-
https://www.google.com/apis/ads/publisher/v202505
Field
ApiError
(inherited) fieldPath
xsd:
string
The OGNL field path to identify cause of error.
fieldPathElements
A parsed copy of the field path. For example, the field path "operations[1].operand" corresponds to this list: {FieldPathElement(field = "operations", index = 1), FieldPathElement(field = "operand", index = null)}.
trigger
xsd:
string
The data that caused the error.
errorString
xsd:
string
A simple string representation of the error and reason.
QuotaError
reason
Enumerations
-
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.
