429 Resource has been exhausted | Too many requests. Retry in 30 seconds

[Frederic Garcia]

Hi,

I have been using the Google Ads HistoricalMetrics API quite successfully for the last few months. However, ever since this morning, I notice an increased error rate with the following message:

An error occurred: 429 Resource has been exhausted (e.g. check quota). [type_url: "type.googleapis.com/google.ads.googleads.v17.errors.GoogleAdsFailure"

I am pretty sure I am following the needed limits. Is there an issue with the rate limiter perhaps? I notice that there's no defined outage in the dasboard, but can someone confirm if I am the only one with this issue?

https://ads.google.com/status/publisher

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

By reviewing your concern, I understand that you are getting "RESOURCE_EXHAUSTED" error, which 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. Also, please check this sample code for how to Handle a Rate Exceeded Error for more information.

In order to investigate the issue further, please provide us with the complete API logs (request and response logs with request-id and request header) generated at your end along with the uncropped UI screenshot (with visible customer Id) to better assist you on this request. 

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGd49:ref" (ADR-00271169)

Thanks,
 

Google Ads API Team

[Paulo Silva]

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

Kindly note that encountering the RESOURCE_EXHAUSTED error when having standard access indicates that you could be performing too many requests within a short period of time, or that the API's servers are imposing a limit based on all users traffic :

• The Google Ads API buckets requests for rate limiting by queries per second (QPS) per client customer ID (CID) and developer token, meaning that metering is enforced independently on both CIDs and developer tokens. The Google Ads API uses a Token Bucket algorithm to meter requests and determine an appropriate QPS limit, so the exact limit will vary depending on the overall server load at any given time.

That said, we recommend mitigating the number of requests being made within a short period of time, checking for any parallel processes that also uses your account and developer token, as well as performing retries and the methods mentioned in the guide, to avoid or manage this error. 

If you are still facing the same issue, kindly provide us with the complete API logs (request and response with request-id and request header) generated at your end.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGd99:ref" (ADR-00271225)

Thanks,
 

Google Ads API Team