I believe the problem on your servers started 15 March 11am NewYork time. 
It's possible that your servers have recovered and it's working better now. 
Your recovery occurred circa 18 Mar 1500 NY time.

I'd still like to know how to stream to your servers via protobuf java sdk. 
I know how to stream from your servers as I said.

On Tuesday 19 March 2024 at 00:49:23 UTC-4 Google Ads API Forum Advisor 
wrote:

> Hi,
>
> Thank you for reaching out to the Google Ads API support team. 
>
> By reviewing your concern, I understand that you aim to transmit data to 
> ConversionUploadServiceClient or a similar service on Google's servers, as 
> you're encountering recurrent failures when dealing with large payloads on 
> this particular service. I would recommend you to kindly refer to the Java 
> sample code 
> <https://developers.google.com/google-ads/api/samples/upload-offline-conversion#java>
>  as 
> it describes on how to use this service while uploading conversions. 
>
> In order to investigate your issue further, 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>
>  
> logs 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 you end along with the uncropped UI screenshot of the Google 
> Ads account of where you are facing this issue. 
>
> 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 in Java 
> <https://developers.google.com/google-ads/api/docs/client-libs/java/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.!5004Q02s01pz:ref" (ADR-00227711)
>
> Thanks,
>   
> [image: Google Logo] Google Ads API Team 
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/7acf30f9-501e-4a83-a39a-4c6309861491n%40googlegroups.com.
  • Ja... dhmitc...@gmail.com
    • ... dhmitc...@gmail.com
      • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
        • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
          • ... Don Mitchell

Reply via email to