RESOURCE_EXHAUSTED error doesn't make sense

[Dmitri Martin]

An automation I set up in Make (formerly Integromat) keeps failing to execute and returning this error:

RESOURCE_EXHAUSTED (429) Resource has been exhausted (e.g. check quota). ◉ Too many requests. Retry in 89 seconds.

I know it's not an issue with Make because the automation sometimes runs successfully. 

The automation (when it works) performs ONE search request each day for Ad Groups that do not have a removed status and returns a BATCH list of them (currently 127) that includes their id, status, and other items.

All but 124 of the ad groups are for driving leads to pages on my website that display properties for sale on one of 62 lakes. Each lake has 2 ad groups that target leads based on different keywords.

However, sometimes there are no properties currently for sale on a lake, so I need the 2 ad groups for that lake to be paused or enabled based on each lake's inventory of listings.

To determine whether to change each ad group's status it iterates thru the BATCH results (instead of making individual API requests) and searches an inventory spreadsheet to determine if the ad group should be paused or enabled.  

If an ad group should be paused, it checks the BATCH results to see if the ad group is already paused. If not, it makes one API request to update the ad group status to paused. The process is vice versa for ad groups that should be active.

On most days, the inventory of listings doesn't change so the update API requests don't even execute. When inventory does change, the most I could see would be up to 5 lakes changing inventory in a day resulting in up to 10 update API requests.

I don't understand how one get request and 10 update requests could cause this error. Based on the API limits published on your website, this is an insignificant amount of requests.  

Why does this keep happening and how can I stop it from continuing to happen?

Dmitri Martin

[Google Ads API Forum Advisor]

Hi Dmitri,

Since it's telling you top retry in a minute and a half I can guess you may be sending in burst mode and would suggest you send one update request which can handle 5,000 mutates instead of 10 update requests.

For us to investigate, could you send us a 'DEBUG' log level request and response log of raw API communications that got you this error?

The request and response appears similar to the JSON Mappings in our REST documentation with additional headers and information such as request Id. Here are logging instructions for our Java, .NET, PHP, Python, Ruby and Perl Ads API Client Libraries.

If you are using our REST interface then the full multi line curl command line is a request log and adding curl command line option '-i' will also generate a response log.

Regards,

Aryeh Google Ads API Team

 

ref:_00D1U1174p._5004Q2dJK8x:ref

[Dmitri Martin]

Thank you for your reply.

The 10 update requests are followed by a 5 second wait but they are not the problem anyway.  As the image I included in my support request shows, the failure happens at the beginning of the automation with the single get request.

I don't have direct access to the raw logs but have emailed Make support requesting them.  

Meanwhile, can you check your own logs for the get request you should have received this morning at 7:33:01 AM?  I don't think you find an error with the request you received since it's worked before and I haven't modified it.

- Dmitri

[Google Ads API Forum Advisor]

Hi Dmitri,

I don't have access to internal logs without a verified reason, and that requires a log.