RESOURCE_EXHAUSTED when upgraded to Standard Access Token

122 views

Skip to first unread message

Hoyman Chen

unread,

May 6, 2023, 7:43:26 AM5/6/23

to Google Ads API and AdWords API Forum

Hi,

Our account was upgraded to Standard Access yesterday, but we are still receiving errors such as and are essentially locked out from making any more calls:

raise exceptions.from_grpc_error(exc) from exc\\ngoogle.api_core.exceptions.ResourceExhausted: 429 Resource has been exhausted (e.g. check quota). [type_url: "type.googleapis.com/google.ads.googleads.v13.errors.GoogleAdsFailure"\\nvalue: "\\\\nc\\\\n\\\\002X\\\\002\\\\022*Too many requests. Retry in 79138 seconds.*1\\\\"/\\\\010\\\\003\\\\022%Number of operations for basic access\\\\032\\\\004\\\\010\\\\242\\\\352\\\\004\\\\022\\\\

The error implies that we exceeded the quota for Basic access but we were already upgraded to Standard Access which should give us unlimited operations a day. Is there a delay? or do we need to do something else on our end.

Thanks

Google Ads API Forum Advisor

unread,

May 8, 2023, 5:26:42 AM5/8/23

to adwor...@googlegroups.com

Hi,

Thank you for reaching out to us.

Since you have encountered the quota_error: RESOURCE_EXHAUSTED, it means that a system frequency limit has been exceeded. Kindly prevent sending too many requests in a short period of time and also ensure to set up short delays between requests or combine more operations in fewer requests. You can check this documentation for more details.

RESOURCE_EXHAUSTED: https://developers.google.com/google-ads/api/reference/rpc/v13/QuotaErrorEnum.QuotaError#resource_exhausted
documentation: https://developers.google.com/google-ads/api/docs/best-practices/common-errors?hl=en#quotaerror

If in the event that you are still encountering the said error after considering the suggestion provided above, then you may provide us with the complete API logs (request and response with request-id) generated on your end so that we can further check this and provide you other appropriate recommendations.

request : https://developers.google.com/google-ads/api/docs/concepts/field-service#request
response: https://developers.google.com/google-ads/api/docs/concepts/field-service#response
request-id : https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id

Note that logs can be requested or provided to the developer handling the Google Ads API transactions when logging of the API requests has been enabled. You may check here and click your client library for the specific guideline to enable it.

here: https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging

For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include the HTTP response headers in the output.

You may then send the requested logs via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Best regards,

Google Ads API Team