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.
On Wednesday, December 20, 2023 at 8:58:55 PM UTC+1 
sandra...@randallreilly.com wrote:

> Everything has been running much better for me since Sunday thankfully. 
> However, perhaps others were or are noticing similar issues.
>
> On Wednesday, December 20, 2023 at 12:02:24 PM UTC-5 Google Ads API Forum 
> Advisor wrote:
>
>> 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* 
>> <https://developers.google.com/google-ads/api/docs/concepts/field-service#request>
>>  and *response* 
>> <https://developers.google.com/google-ads/api/docs/concepts/field-service#response>
>>  with *request-id* 
>> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id>
>>  and *request header* 
>> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers>)
>>  
>> 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* 
>> <https://developers.google.com/google-ads/api/docs/client-libs/java/logging>
>> , *.Net* 
>> <https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging>
>> , *PHP* 
>> <https://developers.google.com/google-ads/api/docs/client-libs/php/logging>
>> , *Python* 
>> <https://developers.google.com/google-ads/api/docs/client-libs/python/logging>
>> , *Ruby* 
>> <https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging>
>>  or *Perl* 
>> <https://developers.google.com/google-ads/api/docs/client-libs/perl/logging> 
>> 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,
>>   
>> [image: Google Logo] Google Ads API Team 
>>
>>  
>>
>>
-- 


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/ 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.wpp.com_WPP_About_&d=DwMFaQ&c=N-xPqDyeLJg5V3gLll2thA&r=aMkvY63z6j7EsF4XIb9BQM9Vg_NPq0Tyq_c4qEjSGuI&m=KGmvFRgWqLXTGN-0TqwJrXtnIjxRssANR2E_1vsPHZg&s=CtJil6FZbGrYDvuuovO87MZKGQbQYXhR41-kweAs1C0&e=>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/6ab63491-064e-4e70-9a43-fb950edb4631n%40googlegroups.com.

Reply via email to