API Issue - High Latency and deadline exceeded errors all of a sudden

[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 two 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

[Matt Dworkin]

In case this is related, we've suddenly been hitting request limits, which shouldn't be happening. Nothing has changed on our end, same number of requests as normal. 

Status code: 8 Details: Resource has been exhausted (e.g. check quota). Failure: {"errors":[{"errorCode":{"quotaError":"RESOURCE_EXHAUSTED"},"message":"Too many requests. Retry in 900 seconds."

[GDZ]

Same here, bunch of Quota errors last several hours

[Google Ads API Forum Advisor]

Hi,

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

The RESOURCE_EXHAUSTED error, 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. Additionally, you may refer to the "Usage flow" guide for insights on incorporating batch processing into your API requests.

To assist you further, please provide us with the below details:

• Affected Customer IDs
• The date the issue started
• How much time you waited before retrying a request
• Also, 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.

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

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-06-23 03:49:14Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rfvrw:ref" (ADR-00315187)

[Arun S R]

I am also facing Same quote issues, same deadline exceeded issues. Quota issues seems to have been resolved. No more resource exhausted errors. But getting deadline exceeded errors whenever I query search_term view report. The client also waits long, and then returns deadline exceeded error. Please help fix this issue.

[Google Ads API Forum Advisor]

Hi,

Kindly note that the  DEADLINE_EXCEEDED error means a search request was made that generated too large of a response, or a mutate request was too large to process. In order to handle this error, I would recommend  you to wait for about 30 seconds, then retry the request. If the error persists try breaking the request into multiple, smaller requests that can be completed more quickly. I suggest you refer to the DEADLINE_EXCEEDED documentation for more information.The RESOURCE_EXHAUSTED error 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.

Also, you refer to the "Batch operations" documentation for more information. Additionally, you may refer to the "Usage flow" guide for insights on incorporating batch processing into your API requests. To assist you further, please provide us with the below details:

• Affected Customer IDs
• The date the issue started
• How much time you waited before retrying a request
• Also, 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.

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

 

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[2025-06-23 10:40:48Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rfvZi:ref" (ADR-00315144)

[Matt Dworkin]

Hi,

To be clear, this quota issue happened out of nowhere. We were sending the same exact amount of requests as normal at the same cadence. The issue seems to have resolved itself, but wanted to flag it in case it was happening to others and something is going on.

[Google Ads API Forum Advisor]

Hi,

Glad that the issue has been resolved. If you face the same issue, then kindly get back to us with the complete API logs (request and response logs with request-id and request header) generated at your end to investigate the issue further.

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[2025-06-23 18:18:50Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rfvZi:ref" (ADR-00315144)

[高新新]

Hi,

I have encountered the same issue. Below are the request logs.

com.google.ads.googleads.v19.errors.GoogleAdsException: errors { error_code { quota_error: RESOURCE_EXHAUSTED } message: "Too many requests. Retry in 900 seconds." } request_id: "M-2M-ZHwCDnozqpOwNSYXQ"

[Google Ads API Forum Advisor]

Hi,

The reported issue has been resolved now. Can you please re-try making the API calls again and let us know if you are still facing the RESOURCE_EXHAUSTED errors?​ ​ 

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[2025-06-30 06:24:01Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rfvZi:ref" (ADR-00315144)

[福堀陽介]

Hi,
Yesterday, we also had the same issue where RESOURCE_EXHAUSTED was returned. (It also happened last week.)
Please investigate this as soon as possible and let us know if there is a problem with the API.

2025年6月24日火曜日 3:19:38 UTC+9 Google Ads API Forum Advisor:

[Google Ads API Forum Advisor]

Hi,

I would like to let you know that this issue has now been resolved. Please try making your API calls again, and let us know if you are still experiencing any problem.
 

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[2025-06-30 10:09:01Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rfvZi:ref" (ADR-00315144)