502 Bad Gateway Errors

[Sandra Brooks]

Is anyone aware of any issues with the Google Ads API? I am seeing everything from increased latency to no response to 502 bad gateway errors today. Everything was fine yesterday.  I have been trying to look at everything I can, but curious if anyone else is seeing an issue.

[GDZ]

Lots of it yesterday and today too.

[Google Ads API Forum Advisor]

Hi,

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

After reviewing your concern, I understand that you are getting Bad Gateway errors from the Google Ads API. In order to assist you further, we would like to see the uncropped UI screenshot of the issue you are facing. Also, Kindly provide us with the 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.

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.!5004Q02r2tf7:ref"

Thanks,
 

Google Ads API Team

 

[sandra...@randallreilly.com]

Everything has been running much better for me since Sunday thankfully. However, perhaps others were or are noticing similar issues.

[Marcel Steinbach]

We've been experiencing this too since at least Dec 14ht. 

I1221 14:24:59.766567339   18437 writing.cc:143]                       CLIENT: Ping sent [ipv4:216.58.212.234:443]: max_pings_without_data: 2, pings_before_data_required: 1, last_ping_sent_time_: @908452ms

WARNING:google.ads.googleads.client:Request made: ClientCustomerId: 1541036133, Host: googleads.googleapis.com, Method: /google.ads.googleads.v13.services.GoogleAdsService/Search, RequestId: None, IsFault: True, FaultMessage: 502:Bad Gateway
WARNING:google_ads_collector:503 502:Bad Gateway, retrying in 1 seconds...
INFO:google_ads_collector:Start fetching data for customer id ***********
I1221 14:31:20.516098447   18447 connectivity_state.cc:183]            ConnectivityStateTracker client_channel[0x7dc9f4044300]: get current state: READY
I1221 14:31:54.549579928   18448 writing.cc:143]                       CLIENT: Ping sent [ipv4:216.58.212.234:443]: max_pings_without_data: 2, pings_before_data_required: 1, last_ping_sent_time_: @1323235ms

After that, the client API is stuck for more than 2h now (this is current)

In the last few days, we've even had jobs that were stuck for almost 12 hours. 

We're using the python google ads sdk google-ads==20.0.0

I can send more details if needed.

Privileged/Confidential Information may be contained in this message. If you are
not the addressee indicated in this message (or responsible for delivery of the
message to such person), you may not copy or deliver this message to anyone. In
such case, you should destroy this message and kindly notify the sender by reply
email. Please advise immediately if you or your employer does not consent to email
for messages of this kind. Opinions, conclusions and other information in this
message that do not relate to the official business of Group M Worldwide LLC and/or
other members of the GroupM group of companies shall be understood as neither given
nor endorsed by it. GroupM is the global media investment management arm of WPP.
For more information on our business ethical standards and Corporate Responsibility
policies please refer to WPP's website at http://www.wpp.com/WPP/About/

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to us.

From the provided information, I observed that you are using v13 version of Google Ads API. Please be informed that the v13 is deprecated from June 7, 2023 and will sunset by January 31, 2024. So, I would suggest you upgrade to v15. For information regarding deprecation and sunset, you can check this reference document.

Also, the logs provided by you are not enough to replicate the issue on our end. Could you please provide us with the complete API logs (request and response with request-id and request header). If possible, provide the updated version logs.pr