Hi Raneen, we face a similar issue for some months now observing requests sporadically failing with 400 Bad Request. Our versions: 201702 version of the AdWords API https://github.com/googleads/googleads-java-lib 3.12
The related log part: 2018-03-19 01:21:15 [WARN] c.g.a.a.a.lib.utils.report_download Request made: Service: reportdownload Method: POST clientCustomerId: 125-142-3890 URL: https://adwords.google.com//api/adwords/reportdownload/v201710 Request ID: null ResponseTime(ms): null OperationsCount: null IsFault: true FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 400: Bad Request 2018-03-19 01:21:15 [ERROR] c.g.a.a.a.l.c.A.soapXmlLogger Couldn't process XML into a Document Best Regards, Ron Am Mittwoch, 10. Januar 2018 11:25:23 UTC+1 schrieb raneenb...@gmail.com: > > Hi Anash, > the failure also happen with other reports. > we think that the problem happen because of that the > AdWordsSession expired . > we have checked in the documentation which error returned if the > AdWordsSession expired . > can you please confirm that we got 400 if the session expired . > > Thanks, > Raneen. > > > On Friday, January 5, 2018 at 4:28:11 PM UTC+2, Anash P. Oommen (AdWords > API Team) wrote: >> >> Hi Raneen, >> >> This looks to me as a combination of two issues - a server issue that's >> occasionally sending 400 responses, and the client library not being able >> to handle it correctly. >> >> For the first part, could you turn on logging and capture a failing >> request? The instructions are here: >> https://github.com/googleads/googleads-java-lib/wiki/Logging. Once you >> have the logs, share it with me using the "Reply privately to author" and >> I'll ask the reporting team to respond. >> >> For the second part, file an issue with the Java client library here: >> https://github.com/googleads/googleads-java-lib/issues. You'd want to >> post a redacted version of the log you are sharing with me privately. >> >> Cheers >> Anash P. Oommen, >> AdWords API Team. >> >> >> On Thursday, January 4, 2018 at 6:37:05 AM UTC-5, Raneen Bsais wrote: >>> >>> Hi Peter, >>> this error not always reprduce , we didn't catch this excption by >>> debugging , it happens sometiems for our clients , >>> and even after the client try again the issue desapper. >>> the main problem that the issue happen and if try it not happen . >>> >>> Regards, >>> Raneen. >>> >>> >>> On Thursday, January 4, 2018 at 7:56:51 AM UTC+2, Peter Oliquino wrote: >>>> >>>> Hi Raneen, >>>> >>>> Thank you for sending the requested information. Upon trying out your >>>> report and by also using the 201702 version of the AdWords API, I was able >>>> to successfully generate it on my end and did not encounter the error 400. >>>> This being said, could you confirm if you are still encountering the issue? >>>> >>>> Best regards, >>>> Peter >>>> AdWords API Team >>>> >>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords 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 "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/3e6150db-9e6a-47ef-a97d-58cb1d271968%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
