Increased number of internal errors received from google ads api

[Brad Hartley]

Over the past two days I have been seeing an alarming amount of internal errors from our request to google. Largely, they have been related to creating user lists and campaigns but also account budget proposals. There havent been any known changes in my code or infrastructure, so I assume something is happening on the google ads side. 

Error response:
{ "created": "@1737738548.515310877", "description": "Error received from peer ipv4:[redacted]:443", "file": "/var/local/git/grpc/src/core/lib/surface/call.cc", "file_line": 953, "grpc_message": "Internal error encountered.", "grpc_status": 13 }

[Ronny Cohen]

I wanted to let you know that I am also experiencing consistent API failures. Every other call I make results in an "Internal error encountered" message.

Please let me know if you have any updates or potential solutions regarding this issue.

Thanks

Ronny

[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 an Internal Error when trying to create a userlist and campaigns. Kindly note Internal Error occurs when something unexpected happens while processing the request. When you retry requests, use an exponential backoff policy. For example, if you first pause 5 seconds before the first retry, you could pause 10 seconds after the second and 20 seconds after the third retry. Exponential backoff helps ensure you are not calling the API too many times.

I suggest you refer to the documentation for more information.

if issue still persists, kindly provide us with the complete API logs (request and response logs with request-id and request header) generated at your end, so that we can investigate this issue further on our end and assist you accordingly.

If you are using a client library and haven't enabled logging yet, I would request that you 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.!5004Q02vGyU3:ref" (ADR-00285920)

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[Brad Hartley]

Will do. Something has definitely changed on the google end as far as I can tell. We have been using the system we have now for years and not seen an error rate like this and we havent increased our volume of request by any large amount. I am taking the advice of the Google Forum Advisor and implementing a better retry system but I am confident there is an issue on their end. These errors are happening across all types of request to create objects using the api. But If I figure out any other solution I will post it here.