High Latency

[Haritha Devalla]

Hi Team,

We are facing high latency with the API calls and are also seeing deadline exceeded errors for most of the accounts for the past eight hours.
Could you please look into this at the earliest and let us know if there is any issue with the API currently.

Thanks,
Haritha

[GDZ]

Double that. Lots of "resource exhausted" and "quota errors" lats 8-9 hours.  Same situation as everybody had back in June. Pls fix ASAP.

[wang davy]

the same , please fix ASAP

[Toshiyuki Maeda]

I'm having the same problem. Could you fix it ASAP, please?

2024年8月30日金曜日 10:33:38 UTC+9 Haritha Devalla:

[Gavin]

+1 We are also experiencing the same issue, starting from 11am PST. It seems to have gotten better since 8pm PST.

Can you please confirm that the issue has been fixed?

Thanks,

Gavin

[Google Ads API Forum Advisor]

Hi,

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

I understand that you have encountered the "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.

Additionally, we also have daily API operation limits where requests that violate these limits are rejected with the error: RESOURCE_EXHAUSTED. You may check out API Limits and Quotas for more information. 

I could see that you only provided the response logs. In order to investigate the issue further, provide us with the updated complete API logs (request body and request-id and request header) generated at your end to assist you better.

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.!5004Q02vFXeE:ref" (ADR-00265635)

Thanks,
 

Google Ads API Team

[D. H.]

We are hitting frequent "resource exhausted" errors as well.

Is it possible to use batch jobs to get reports from a large number of accounts?

[Google Ads API Forum Advisor]

Hi,

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

As per provided information, I could see that you are encountering the RESOURCE_EXHAUSTED error, which generally occurs when you are sending too many requests in a short period of time. The server displays this error once it detects that your request has exceeded the system frequency limit. I would recommend giving short delays between requests or combining more operations in fewer requests. Also, you refer to the "Batch operations" documentation for more information. In order to assist you further, could you please provide us with the below information:

• Affected Customer Id
• Date of this issue started
• How much time did you wait before retry of a request
• Confirm whether you are having the same delays for other services too
• 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.
 

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

Thanks,
 

Google Ads API Team

[Google Ads API Forum Advisor]

Hi,

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

I understand that you have encountered the "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.

Additionally, we also have daily API operation limits where requests that violate these limits are rejected with the error: RESOURCE_EXHAUSTED. You may check out API Limits and Quotas for more information. 

In order to debug the issue further please provide us with the below details.

• Provide us with the complete API logs (request and response logs 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.
• The dates that you started experiencing the issue. 
• Affected customer ID. 

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.!5004Q02vFXmc:ref" (ADR-00265655)

Thanks,
 

Google Ads API Team

[Google Ads API Forum Advisor]

Hi,

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

I understand that you have encountered the "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.

Additionally, we also have daily API operation limits where requests that violate these limits are rejected with the error: RESOURCE_EXHAUSTED. You may check out API Limits and Quotas for more information. 

In order to debug the issue further, please provide us with the below details.

• Provide us with the complete API logs (request and response logs 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.
• The dates that you started experiencing the issue. 
• Affected customer ID. 

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.!5004Q02vFXxu:ref" (ADR-00265676)

Thanks,
 

Google Ads API Team

[D. H.]

Hi Google Ads Support,

My question from the previous message: Is it possible to use batch jobs to get reports from a large number of accounts?

The reason for asking is we are hitting frequent "resource exhausted" errors when requesting reports via the Google Ads API.

Your answer links to the "Batch operations" documentation. As you linked to the documentation, can you please share an example for how batch operations can be used with the Google Ads API for retrieving Google Ads reports, asynchronously, so as to avoid "resource exhausted" and similar errors?

Thanks,

D.H.

[Google Ads API Forum Advisor]

Hi,

It's not possible to use the batch operations for the Google Ads API for retrieving Google Ads reports. The Google Ads API enforces limits on API operations, such as the number of operations that can be sent to a single mutate request. I would recommend you to kindly refer to the API Limits and Quotas documentation for more information. This error may also occur if you have already exceeded the daily limit of 15,000 API operations per day. Additionally, the "RESOURCE_EXHAUSTED" error can be mitigated by increasing the number of operations per day. If you would like to apply for unlimited Google Ads API operations, fill out the standard access application form. I would suggest you please refer to this “Access Levels and Permissible Use” documentation for more information.

If you are getting a RESOURCE_EXHAUSTED error even after having the standard access, then we would require information about one instance of where you are facing this error for further investigation, so I would request you to provide the complete API logs (request and response logs with request-id and request header) generated at your end to assist you in a better manner.

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. You can enable logging via the curl command by using the -i flag for REST interface requests. 

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.!5004Q02vFYM7:ref" (ADR-00265706)

Thanks,
 

Google Ads API Team