Increased DEADLINE_EXCEEDED errors

[NET_Api_User]

Dear team,

There are increased DEADLINE_EXCEEDED AND INTERNAL_ERROR from the API as the time of this post. Is someone looking into this please?

Regards,

M

[Google Ads API Forum Advisor]

Hi,

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

 

From the provided information, you are getting the error DEADLINE_EXCEEDED, which indicates that your request took longer than the deadline. That said, you may check this example to set custom client timeouts and this documentation for more information in timeouts. Note that you can set the timeout to 2 hours or more, but the API may still time out extremely long-running requests and return a DEADLINE_EXCEEDED error.

Regarding the INTERNAL_ERROR occurs when something unexpected happens while processing the request. The common cause could be the API isn't functioning correctly. However, this is transient in nature and the API request will work again when retrying it after 30 seconds or some time. You may also retry any requests that failed with this error, using an exponential backoff schedule for the retries. Here is a code example demonstrating how to implement an exponential back off strategy.

If the issue still persists, then provide us with the below information, so that we can investigate this issue further.

• Date of this issue started
• How much time did you wait before retry of a request
• Updated complete API 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-12-01 10:06:25Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vUaCq:ref" (ADR-00346269)