RE: throwing DetailedReportDownloadResponseException with 400 Response code.

[googleadsapi-forumadvisor via AdWords API and Google Ads API Forum]

Hi all,

I haven't been able to locate the failed requests in our logs from earlier
this month, but if you're still encountering this error regularly please
let me know.

Thanks,
Josh, Google Ads API Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/04/19 13:42:47 googleadsapi-forumadvi...@google.com wrote:

Hi,

Could you share the date and time, including time zone, of the failed
request below so I can look it up in our logs?

Thanks,
Josh, AdWords API Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/03/19 14:32:14 sampz...@gmail.com wrote:

Hi

I believe i am getting similar issue. It was working arround 8 hours ago.

 c.g.a.a.a.lib.utils.report_download  : Request made: Service:
reportdownload Method: POST clientCustomerId: URL:
https://adwords.google.com//api/adwords/reportdownload/v201809 Request ID:
null ResponseTime(ms): null OperationsCount: null IsFault: true
FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 400:
Bad Request
2019-03-03 19:13:20.430  INFO 17416 --- [ool-17-thread-4]
c.g.a.a.a.lib.utils.report_download  : HTTP request:
accept-encoding: [gzip]
authorization: REDACTED
user-agent: [unknown (AwApi-Java, AdWords-Axis/4.4.0, Common-Java/4.4.0,
Axis/1.4, Java/1.8.0_171, maven)]
developertoken: REDACTED
clientcustomerid: 
skipreportheader: false
skipcolumnheader: false
skipreportsummary: false
includezeroimpressions: false

Content:
__rdxml: standalone="yes"?>
xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201809
">IdAdGroupIdDate<
ns2:fields>CampaignIdCampaignNameAdGroupNameCriteria
ImpressionsCtrCostConversionRate
ConversionsClicksAGE_RANGE_PERFORMANCE_REPORTAGE_RANGE_PERFORMANCE_REPORTCSV



On Saturday, 11 August 2018 15:45:35 UTC+1, Josh Radcliff (AdWords API
Team) wrote:

Hi,

Thanks, everyone, for your patience while we tracked down the root cause of
this issue. The problem was that when a specific transient error occurred
during processing on our side, it was being incorrectly reported back in
the response  with status code 400 (bad request). A fix was deployed so
that the proper status code of 500 (internal server error) will now be
returned in this situation.

Best regards,
Josh, AdWords API Team

On Thursday, July 26, 2018 at 9:09:47 AM UTC-4, Josh Radcliff (AdWords API
Team) wrote:

Hi,

We've identified the root cause and are working on a fix. I'll update this
discussion once the fix has been deployed.

Thanks,
Josh, AdWords API Team

On Friday, July 20, 2018 at 9:43:45 AM UTC-4, Josh Radcliff (AdWords API
Team) wrote:

Hi Arthur,

Does the same request succeed on retry? If so, then you are encountering
the same issue being discussed here. I advise having retry logic in your
reporting jobs, both in general and to mitigate this particular issue.

Also, please note that v201710 will be sunset on July 25
.
Please make sure you migrate to a newer version

of the AdWords API before that date.

Thanks,
Josh, AdWords API Team

On Thursday, July 19, 2018 at 4:50:57 PM UTC-4, arthur@brainweb.com.br
wrote:

Hello everyone,

I'm working on an application that retrieves data from the Adwords API and
I'm facing the same 400 - Bad Request problem. We are working with the
v201710 version.
Yesterday I worked normally on the application and today when I arrived I
faced the exact same problem reported here. I didn't change anything in the
code that was working just yesterday!
I spent a lot of time searching for a possible mistake and just want to
make sure that it might not be an error from my part.

Thanks a lot for your attention!

best regards,

Arthur

Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff (AdWords
API Team) escreveu:

Hi Zweitze,

Thanks for providing those details. The engineer investigating this said
they'll be quite helpful. I'll reply back when he has an update.

Cheers,
Josh, AdWords API Team

On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:

This error was away at my site for quite a few weeks, but reappeared this
morning. The response headers that came with the error were:

Content-Disposition /bigstore/aw3-webapi-report-do
wnload/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-nu
ll-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
X-Content-Type-Options nosniff
X-Frame-Options SAMEORIGIN
X-XSS-Protection 1; mode=block
Alt-Svc quic=":443"; ma=2592000; 

RE: throwing DetailedReportDownloadResponseException with 400 Response code.

[googleadsapi-forumadvisor via AdWords API and Google Ads API Forum]

Hi,

Could you share the date and time, including time zone, of the failed
request below so I can look it up in our logs?

Thanks,
Josh, AdWords API Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/03/19 14:32:14 sampz...@gmail.com wrote:

Hi

I believe i am getting similar issue. It was working arround 8 hours ago.

 c.g.a.a.a.lib.utils.report_download  : Request made: Service:
reportdownload Method: POST clientCustomerId: URL:
https://adwords.google.com//api/adwords/reportdownload/v201809 Request ID:
null ResponseTime(ms): null OperationsCount: null IsFault: true
FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 400:
Bad Request
2019-03-03 19:13:20.430  INFO 17416 --- [ool-17-thread-4]
c.g.a.a.a.lib.utils.report_download  : HTTP request:
accept-encoding: [gzip]
authorization: REDACTED
user-agent: [unknown (AwApi-Java, AdWords-Axis/4.4.0, Common-Java/4.4.0,
Axis/1.4, Java/1.8.0_171, maven)]
developertoken: REDACTED
clientcustomerid: 
skipreportheader: false
skipcolumnheader: false
skipreportsummary: false
includezeroimpressions: false

Content:
__rdxml: https://adwords.google.com/api/adwords/cm/v201809
">IdAdGroupIdDateCampaignIdCampaignNameAdGroupNameCriteriaImpressionsCtrCostConversionRateConversionsClicksAGE_RANGE_PERFORMANCE_REPORTAGE_RANGE_PERFORMANCE_REPORTCSV



On Saturday, 11 August 2018 15:45:35 UTC+1, Josh Radcliff (AdWords API
Team) wrote:

Hi,

Thanks, everyone, for your patience while we tracked down the root cause of
this issue. The problem was that when a specific transient error occurred
during processing on our side, it was being incorrectly reported back in
the response  with status code 400 (bad request). A fix was deployed so
that the proper status code of 500 (internal server error) will now be
returned in this situation.

Best regards,
Josh, AdWords API Team

On Thursday, July 26, 2018 at 9:09:47 AM UTC-4, Josh Radcliff (AdWords API
Team) wrote:

Hi,

We've identified the root cause and are working on a fix. I'll update this
discussion once the fix has been deployed.

Thanks,
Josh, AdWords API Team

On Friday, July 20, 2018 at 9:43:45 AM UTC-4, Josh Radcliff (AdWords API
Team) wrote:

Hi Arthur,

Does the same request succeed on retry? If so, then you are encountering
the same issue being discussed here. I advise having retry logic in your
reporting jobs, both in general and to mitigate this particular issue.

Also, please note that v201710 will be sunset on July 25
.
Please make sure you migrate to a newer version

of the AdWords API before that date.

Thanks,
Josh, AdWords API Team

On Thursday, July 19, 2018 at 4:50:57 PM UTC-4, arthur@brainweb.com.br
wrote:

Hello everyone,

I'm working on an application that retrieves data from the Adwords API and
I'm facing the same 400 - Bad Request problem. We are working with the
v201710 version.
Yesterday I worked normally on the application and today when I arrived I
faced the exact same problem reported here. I didn't change anything in the
code that was working just yesterday!
I spent a lot of time searching for a possible mistake and just want to
make sure that it might not be an error from my part.

Thanks a lot for your attention!

best regards,

Arthur

Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff (AdWords
API Team) escreveu:

Hi Zweitze,

Thanks for providing those details. The engineer investigating this said
they'll be quite helpful. I'll reply back when he has an update.

Cheers,
Josh, AdWords API Team

On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:

This error was away at my site for quite a few weeks, but reappeared this
morning. The response headers that came with the error were:

Content-Disposition /bigstore/aw3-webapi-report-
download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-
null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
X-Content-Type-Options nosniff
X-Frame-Options SAMEORIGIN
X-XSS-Protection 1; mode=block
Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
Content-Length 0
Cache-Control private, max-age=0
Content-Type application/x-gzip; charset=UTF-8
Date Tue, 17 Jul 2018 04:42:09 GMT
Expires Tue, 17 Jul 2018 04:42:09 GMT
Server GSE

The error occured with some old code running v201710.
CustomerId and ReportDefinition are available if necessary, but I can
assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT
this time) was successfully used thousands of times.



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

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[samson Odubanjo]

Hi

I believe i am getting similar issue. It was working arround 8 hours ago.

 c.g.a.a.a.lib.utils.report_download  : Request made: Service: 
reportdownload Method: POST clientCustomerId: URL: 
https://adwords.google.com//api/adwords/reportdownload/v201809 Request ID: 
null ResponseTime(ms): null OperationsCount: null IsFault: true 
FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 400: 
Bad Request
2019-03-03 19:13:20.430  INFO 17416 --- [ool-17-thread-4] 
c.g.a.a.a.lib.utils.report_download  : HTTP request:
accept-encoding: [gzip]
authorization: REDACTED
user-agent: [unknown (AwApi-Java, AdWords-Axis/4.4.0, Common-Java/4.4.0, 
Axis/1.4, Java/1.8.0_171, maven)]
developertoken: REDACTED
clientcustomerid: 
skipreportheader: false
skipcolumnheader: false
skipreportsummary: false
includezeroimpressions: false

Content:
__rdxml: https://adwords.google.com/api/adwords/cm/v201809;>IdAdGroupIdDateCampaignIdCampaignNameAdGroupNameCriteriaImpressionsCtrCostConversionRateConversionsClicksAGE_RANGE_PERFORMANCE_REPORTAGE_RANGE_PERFORMANCE_REPORTCSV



On Saturday, 11 August 2018 15:45:35 UTC+1, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> Thanks, everyone, for your patience while we tracked down the root cause 
> of this issue. The problem was that when a specific transient error 
> occurred during processing on our side, it was being incorrectly reported 
> back in the response  with status code 400 (bad request). A fix was 
> deployed so that the proper status code of 500 (internal server error) will 
> now be returned in this situation.
>
> Best regards,
> Josh, AdWords API Team
>
> On Thursday, July 26, 2018 at 9:09:47 AM UTC-4, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi,
>>
>> We've identified the root cause and are working on a fix. I'll update 
>> this discussion once the fix has been deployed.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, July 20, 2018 at 9:43:45 AM UTC-4, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Arthur,
>>>
>>> Does the same request succeed on retry? If so, then you are encountering 
>>> the same issue being discussed here. I advise having retry logic in your 
>>> reporting jobs, both in general and to mitigate this particular issue.
>>>
>>> Also, please note that v201710 will be sunset on July 25 
>>> .
>>>  
>>> Please make sure you migrate to a newer version 
>>> 
>>>  
>>> of the AdWords API before that date.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Thursday, July 19, 2018 at 4:50:57 PM UTC-4, 
>>> arthur@brainweb.com.br  wrote:

 Hello everyone,

 I'm working on an application that retrieves data from the Adwords API 
 and I'm facing the same 400 - Bad Request problem. We are working with the 
 v201710 version. 
 Yesterday I worked normally on the application and today when I arrived 
 I faced the exact same problem reported here. I didn't change anything in 
 the code that was working just yesterday! 
 I spent a lot of time searching for a possible mistake and just want to 
 make sure that it might not be an error from my part.

 Thanks a lot for your attention!

 best regards,

 Arthur

 Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff 
 (AdWords API Team) escreveu:
>
> Hi Zweitze,
>
> Thanks for providing those details. The engineer investigating this 
> said they'll be quite helpful. I'll reply back when he has an update.
>
> Cheers,
> Josh, AdWords API Team
>
> On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>>
>> This error was away at my site for quite a few weeks, but reappeared 
>> this morning. The response headers that came with the error were:
>>
>> Content-Disposition 
>> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
>> X-Content-Type-Options nosniff
>> X-Frame-Options SAMEORIGIN
>> X-XSS-Protection 1; mode=block
>> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
>> Content-Length 0
>> Cache-Control private, max-age=0
>> Content-Type application/x-gzip; charset=UTF-8
>> Date Tue, 17 Jul 2018 04:42:09 GMT
>> Expires Tue, 17 Jul 2018 04:42:09 GMT
>> Server GSE
>>
>> The error occured with some old code running v201710.
>> CustomerId and ReportDefinition are available if necessary, but I can 
>> assure you that that same ReportDefinition (a 
>> PLACEMENT_PERFORMANCE_REPORT 
>> this time) was successfully used thousands of times.
>>
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

Thanks, everyone, for your patience while we tracked down the root cause of 
this issue. The problem was that when a specific transient error occurred 
during processing on our side, it was being incorrectly reported back in 
the response  with status code 400 (bad request). A fix was deployed so 
that the proper status code of 500 (internal server error) will now be 
returned in this situation.

Best regards,
Josh, AdWords API Team

On Thursday, July 26, 2018 at 9:09:47 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> We've identified the root cause and are working on a fix. I'll update this 
> discussion once the fix has been deployed.
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, July 20, 2018 at 9:43:45 AM UTC-4, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Arthur,
>>
>> Does the same request succeed on retry? If so, then you are encountering 
>> the same issue being discussed here. I advise having retry logic in your 
>> reporting jobs, both in general and to mitigate this particular issue.
>>
>> Also, please note that v201710 will be sunset on July 25 
>> .
>>  
>> Please make sure you migrate to a newer version 
>> 
>>  
>> of the AdWords API before that date.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, July 19, 2018 at 4:50:57 PM UTC-4, 
>> arthur.baldu...@brainweb.com.br wrote:
>>>
>>> Hello everyone,
>>>
>>> I'm working on an application that retrieves data from the Adwords API 
>>> and I'm facing the same 400 - Bad Request problem. We are working with the 
>>> v201710 version. 
>>> Yesterday I worked normally on the application and today when I arrived 
>>> I faced the exact same problem reported here. I didn't change anything in 
>>> the code that was working just yesterday! 
>>> I spent a lot of time searching for a possible mistake and just want to 
>>> make sure that it might not be an error from my part.
>>>
>>> Thanks a lot for your attention!
>>>
>>> best regards,
>>>
>>> Arthur
>>>
>>> Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff 
>>> (AdWords API Team) escreveu:

 Hi Zweitze,

 Thanks for providing those details. The engineer investigating this 
 said they'll be quite helpful. I'll reply back when he has an update.

 Cheers,
 Josh, AdWords API Team

 On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>
> This error was away at my site for quite a few weeks, but reappeared 
> this morning. The response headers that came with the error were:
>
> Content-Disposition 
> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
> X-Content-Type-Options nosniff
> X-Frame-Options SAMEORIGIN
> X-XSS-Protection 1; mode=block
> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
> Content-Length 0
> Cache-Control private, max-age=0
> Content-Type application/x-gzip; charset=UTF-8
> Date Tue, 17 Jul 2018 04:42:09 GMT
> Expires Tue, 17 Jul 2018 04:42:09 GMT
> Server GSE
>
> The error occured with some old code running v201710.
> CustomerId and ReportDefinition are available if necessary, but I can 
> assure you that that same ReportDefinition (a 
> PLACEMENT_PERFORMANCE_REPORT 
> this time) was successfully used thousands of times.
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads 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/dc384749-6710-4c18-b2f1-97eb500e89f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

We've identified the root cause and are working on a fix. I'll update this 
discussion once the fix has been deployed.

Thanks,
Josh, AdWords API Team

On Friday, July 20, 2018 at 9:43:45 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Arthur,
>
> Does the same request succeed on retry? If so, then you are encountering 
> the same issue being discussed here. I advise having retry logic in your 
> reporting jobs, both in general and to mitigate this particular issue.
>
> Also, please note that v201710 will be sunset on July 25 
> .
>  
> Please make sure you migrate to a newer version 
> 
>  
> of the AdWords API before that date.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, July 19, 2018 at 4:50:57 PM UTC-4, 
> arthur.baldu...@brainweb.com.br wrote:
>>
>> Hello everyone,
>>
>> I'm working on an application that retrieves data from the Adwords API 
>> and I'm facing the same 400 - Bad Request problem. We are working with the 
>> v201710 version. 
>> Yesterday I worked normally on the application and today when I arrived I 
>> faced the exact same problem reported here. I didn't change anything in the 
>> code that was working just yesterday! 
>> I spent a lot of time searching for a possible mistake and just want to 
>> make sure that it might not be an error from my part.
>>
>> Thanks a lot for your attention!
>>
>> best regards,
>>
>> Arthur
>>
>> Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff 
>> (AdWords API Team) escreveu:
>>>
>>> Hi Zweitze,
>>>
>>> Thanks for providing those details. The engineer investigating this said 
>>> they'll be quite helpful. I'll reply back when he has an update.
>>>
>>> Cheers,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:

 This error was away at my site for quite a few weeks, but reappeared 
 this morning. The response headers that came with the error were:

 Content-Disposition 
 /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
 X-Content-Type-Options nosniff
 X-Frame-Options SAMEORIGIN
 X-XSS-Protection 1; mode=block
 Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
 Content-Length 0
 Cache-Control private, max-age=0
 Content-Type application/x-gzip; charset=UTF-8
 Date Tue, 17 Jul 2018 04:42:09 GMT
 Expires Tue, 17 Jul 2018 04:42:09 GMT
 Server GSE

 The error occured with some old code running v201710.
 CustomerId and ReportDefinition are available if necessary, but I can 
 assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
 this time) was successfully used thousands of times.





-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads 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/b6a48e3f-4153-4f63-989c-c36bb87803a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Arthur,

Does the same request succeed on retry? If so, then you are encountering 
the same issue being discussed here. I advise having retry logic in your 
reporting jobs, both in general and to mitigate this particular issue.

Also, please note that v201710 will be sunset on July 25 
.
 
Please make sure you migrate to a newer version 

 
of the AdWords API before that date.

Thanks,
Josh, AdWords API Team

On Thursday, July 19, 2018 at 4:50:57 PM UTC-4, 
arthur.baldu...@brainweb.com.br wrote:
>
> Hello everyone,
>
> I'm working on an application that retrieves data from the Adwords API and 
> I'm facing the same 400 - Bad Request problem. We are working with the 
> v201710 version. 
> Yesterday I worked normally on the application and today when I arrived I 
> faced the exact same problem reported here. I didn't change anything in the 
> code that was working just yesterday! 
> I spent a lot of time searching for a possible mistake and just want to 
> make sure that it might not be an error from my part.
>
> Thanks a lot for your attention!
>
> best regards,
>
> Arthur
>
> Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff 
> (AdWords API Team) escreveu:
>>
>> Hi Zweitze,
>>
>> Thanks for providing those details. The engineer investigating this said 
>> they'll be quite helpful. I'll reply back when he has an update.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>>>
>>> This error was away at my site for quite a few weeks, but reappeared 
>>> this morning. The response headers that came with the error were:
>>>
>>> Content-Disposition 
>>> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
>>> X-Content-Type-Options nosniff
>>> X-Frame-Options SAMEORIGIN
>>> X-XSS-Protection 1; mode=block
>>> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
>>> Content-Length 0
>>> Cache-Control private, max-age=0
>>> Content-Type application/x-gzip; charset=UTF-8
>>> Date Tue, 17 Jul 2018 04:42:09 GMT
>>> Expires Tue, 17 Jul 2018 04:42:09 GMT
>>> Server GSE
>>>
>>> The error occured with some old code running v201710.
>>> CustomerId and ReportDefinition are available if necessary, but I can 
>>> assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
>>> this time) was successfully used thousands of times.
>>>
>>>
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads 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/3e643199-e70b-4980-ad71-93c769d8a808%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[arthur . balduini]

hell

Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff (AdWords 
API Team) escreveu:
>
> Hi Zweitze,
>
> Thanks for providing those details. The engineer investigating this said 
> they'll be quite helpful. I'll reply back when he has an update.
>
> Cheers,
> Josh, AdWords API Team
>
> On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>>
>> This error was away at my site for quite a few weeks, but reappeared this 
>> morning. The response headers that came with the error were:
>>
>> Content-Disposition 
>> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
>> X-Content-Type-Options nosniff
>> X-Frame-Options SAMEORIGIN
>> X-XSS-Protection 1; mode=block
>> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
>> Content-Length 0
>> Cache-Control private, max-age=0
>> Content-Type application/x-gzip; charset=UTF-8
>> Date Tue, 17 Jul 2018 04:42:09 GMT
>> Expires Tue, 17 Jul 2018 04:42:09 GMT
>> Server GSE
>>
>> The error occured with some old code running v201710.
>> CustomerId and ReportDefinition are available if necessary, but I can 
>> assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
>> this time) was successfully used thousands of times.
>>
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads 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/d35c04d5-3d56-4625-a47b-0d97747f09bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[arthur . balduini]

Hello everyone,

I'm working on an application that retrieves data from the Adwords API and 
I'm facing the same 400 - Bad Request problem. We are working with the 
v201710 version. 
Yesterday I worked normally on the application and today when I arrived I 
faced the exact same problem reported here. I didn't change anything in the 
code that was working just yesterday! 
I spent a lot of time searching for a possible mistake and just want to 
make sure that it might not be an error from my part.

Thanks a lot for your attention!

best regards,

Arthur

Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff (AdWords 
API Team) escreveu:
>
> Hi Zweitze,
>
> Thanks for providing those details. The engineer investigating this said 
> they'll be quite helpful. I'll reply back when he has an update.
>
> Cheers,
> Josh, AdWords API Team
>
> On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>>
>> This error was away at my site for quite a few weeks, but reappeared this 
>> morning. The response headers that came with the error were:
>>
>> Content-Disposition 
>> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
>> X-Content-Type-Options nosniff
>> X-Frame-Options SAMEORIGIN
>> X-XSS-Protection 1; mode=block
>> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
>> Content-Length 0
>> Cache-Control private, max-age=0
>> Content-Type application/x-gzip; charset=UTF-8
>> Date Tue, 17 Jul 2018 04:42:09 GMT
>> Expires Tue, 17 Jul 2018 04:42:09 GMT
>> Server GSE
>>
>> The error occured with some old code running v201710.
>> CustomerId and ReportDefinition are available if necessary, but I can 
>> assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
>> this time) was successfully used thousands of times.
>>
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads 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/2a14dffe-9480-43cd-b8de-0486b0fabf1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Zweitze,

Thanks for providing those details. The engineer investigating this said 
they'll be quite helpful. I'll reply back when he has an update.

Cheers,
Josh, AdWords API Team

On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>
> This error was away at my site for quite a few weeks, but reappeared this 
> morning. The response headers that came with the error were:
>
> Content-Disposition 
> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
> X-Content-Type-Options nosniff
> X-Frame-Options SAMEORIGIN
> X-XSS-Protection 1; mode=block
> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
> Content-Length 0
> Cache-Control private, max-age=0
> Content-Type application/x-gzip; charset=UTF-8
> Date Tue, 17 Jul 2018 04:42:09 GMT
> Expires Tue, 17 Jul 2018 04:42:09 GMT
> Server GSE
>
> The error occured with some old code running v201710.
> CustomerId and ReportDefinition are available if necessary, but I can 
> assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
> this time) was successfully used thousands of times.
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads 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/b6cd9682-265f-4240-bf39-4b28e4e74358%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Zweitze]

This error was away at my site for quite a few weeks, but reappeared this 
morning. The response headers that came with the error were:

Content-Disposition 
/bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
X-Content-Type-Options nosniff
X-Frame-Options SAMEORIGIN
X-XSS-Protection 1; mode=block
Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
Content-Length 0
Cache-Control private, max-age=0
Content-Type application/x-gzip; charset=UTF-8
Date Tue, 17 Jul 2018 04:42:09 GMT
Expires Tue, 17 Jul 2018 04:42:09 GMT
Server GSE

The error occured with some old code running v201710.
CustomerId and ReportDefinition are available if necessary, but I can 
assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
this time) was successfully used thousands of times.



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads 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/3fa14949-22b2-4f45-8830-385d4b93a98a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['AdWords API Advisor' via AdWords API and Google Ads API Forum]

Hi Ron,

I've been checking in with them on a regular basis, but unfortunately I 
don't have any progress to report yet.

Thanks,
Josh, AdWords API Team

On Friday, June 22, 2018 at 10:08:21 AM UTC-4, Ronald Findling wrote:
>
> Is there some feedback from the engineering team?
>
> Am Donnerstag, 17. Mai 2018 16:44:27 UTC+2 schrieb Josh Radcliff (AdWords 
> API Team):
>>
>> Hi Ron,
>>
>> The engineering team is still digging into this. I'll be sure to update 
>> this thread as soon as I have more information.
>>
>> In the meantime, please retry the requests as Dorian suggested earlier.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, May 16, 2018 at 4:34:19 PM UTC-4, Ronald Findling wrote:
>>>
>>> Hi Josh,
>>>
>>> are there any updates on this topic? We are eagerly awaiting your 
>>> response on this one.
>>>
>>> Best Regards,
>>> Ron
>>>
>>> Am Freitag, 4. Mai 2018 21:18:47 UTC+2 schrieb Josh Radcliff (AdWords 
>>> API Team):

 Hi Dorian,

 Tracking down the root cause is proving quite challenging, so I don't 
 have any news to report just yet. In the meantime, retrying failed 
 requests 
 (provided you're confident the request is valid) is a good approach.

 Thanks,
 Josh, AdWords API Team

 On Friday, May 4, 2018 at 7:32:45 AM UTC-4, Dorian Kind wrote:
>
> Hi Josh,
>
> any updates on this topic? Can we just retry downloads that fail with 
> this specific error condition (400 HTTP status code and no response 
> content) for the time being?
>
> Thanks for your feedback and best regards,
> Dorian
>
> On Monday, 23 April 2018 14:52:50 UTC+2, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Ron,
>>
>> Thanks for getting back to me. I think we have enough examples now to 
>> track this down. The eng team is making progress, but I don't have any 
>> updates to report just yet. I'll reply back as soon as I have more info.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>>>
>>> Taking into account the daylight savings we currently have UTC+2.
>>> Concerning the 502 unfortionately I don't have the logs at hand any 
>>> more -- but what I remember was an 502 which resulted in a 400 in our 
>>> usage 
>>> of the library.
>>>
>>> Best Regards,
>>> Ron
>>>
>>> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff 
>>> (AdWords API Team):

 Also, I forgot to ask: is that timestamp in CST?

 Thanks,
 Josh, AdWords API Team

 On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff 
 (AdWords API Team) wrote:
>
> Hi Ron,
>
> I'm a little perplexed by the most recent example. I see it shows 
> both:
>
> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad 
> Gateway
>
> and:
>
> Caused by: HTTP Response Code: *400*
>
> Was that a bad copy/paste, or are you actually seeing both 502 and 
> 400 mentioned within the same error?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling 
> wrote:
>>
>> After adding some more logging, another example that results in a 
>> 400 on our side:
>>
>>
>> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
>> Service: reportdownload Method: POST clientCustomerId: XXX 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: 
>> 502: 
>> Bad Gateway
>> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download 
>> HTTP request:
>> accept-encoding: [gzip]
>> authorization: REDACTED
>> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
>> maven, ReportDownloader)]
>> developertoken: REDACTED
>> clientcustomerid: XXX
>> includezeroimpressions: false
>>
>> Content:
>> __rdquery: SELECT Conversions,ConversionValue FROM 
>> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
>> 20180316,20180415
>> __fmt: XML
>>
>> Caused by: HTTP Response Code: 400 at 
>> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>>
>> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff 
>> (AdWords API Team):
>>>
>>> Hi Ron,
>>>
>>> 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Ronald Findling]

Is there some feedback from the engineering team?

Am Donnerstag, 17. Mai 2018 16:44:27 UTC+2 schrieb Josh Radcliff (AdWords 
API Team):
>
> Hi Ron,
>
> The engineering team is still digging into this. I'll be sure to update 
> this thread as soon as I have more information.
>
> In the meantime, please retry the requests as Dorian suggested earlier.
>
> Thanks,
> Josh, AdWords API Team
>
> On Wednesday, May 16, 2018 at 4:34:19 PM UTC-4, Ronald Findling wrote:
>>
>> Hi Josh,
>>
>> are there any updates on this topic? We are eagerly awaiting your 
>> response on this one.
>>
>> Best Regards,
>> Ron
>>
>> Am Freitag, 4. Mai 2018 21:18:47 UTC+2 schrieb Josh Radcliff (AdWords API 
>> Team):
>>>
>>> Hi Dorian,
>>>
>>> Tracking down the root cause is proving quite challenging, so I don't 
>>> have any news to report just yet. In the meantime, retrying failed requests 
>>> (provided you're confident the request is valid) is a good approach.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Friday, May 4, 2018 at 7:32:45 AM UTC-4, Dorian Kind wrote:

 Hi Josh,

 any updates on this topic? Can we just retry downloads that fail with 
 this specific error condition (400 HTTP status code and no response 
 content) for the time being?

 Thanks for your feedback and best regards,
 Dorian

 On Monday, 23 April 2018 14:52:50 UTC+2, Josh Radcliff (AdWords API 
 Team) wrote:
>
> Hi Ron,
>
> Thanks for getting back to me. I think we have enough examples now to 
> track this down. The eng team is making progress, but I don't have any 
> updates to report just yet. I'll reply back as soon as I have more info.
>
> Cheers,
> Josh, AdWords API Team
>
> On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>>
>> Taking into account the daylight savings we currently have UTC+2.
>> Concerning the 502 unfortionately I don't have the logs at hand any 
>> more -- but what I remember was an 502 which resulted in a 400 in our 
>> usage 
>> of the library.
>>
>> Best Regards,
>> Ron
>>
>> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff 
>> (AdWords API Team):
>>>
>>> Also, I forgot to ask: is that timestamp in CST?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff 
>>> (AdWords API Team) wrote:

 Hi Ron,

 I'm a little perplexed by the most recent example. I see it shows 
 both:

 com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad 
 Gateway

 and:

 Caused by: HTTP Response Code: *400*

 Was that a bad copy/paste, or are you actually seeing both 502 and 
 400 mentioned within the same error?

 Thanks,
 Josh, AdWords API Team

 On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling 
 wrote:
>
> After adding some more logging, another example that results in a 
> 400 on our side:
>
>
> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
> Service: reportdownload Method: POST clientCustomerId: XXX 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: 
> 502: 
> Bad Gateway
> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download 
> HTTP request:
> accept-encoding: [gzip]
> authorization: REDACTED
> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
> maven, ReportDownloader)]
> developertoken: REDACTED
> clientcustomerid: XXX
> includezeroimpressions: false
>
> Content:
> __rdquery: SELECT Conversions,ConversionValue FROM 
> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
> 20180316,20180415
> __fmt: XML
>
> Caused by: HTTP Response Code: 400 at 
> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>
> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff 
> (AdWords API Team):
>>
>> Hi Ron,
>>
>> Sorry, I'm still having trouble locating those requests in our 
>> logs. Would you mind sending over the customer ID where your 
>> developer 
>> token is registered? You can send it only to me by clicking *Reply 
>> privately to author*.
>>
>> Regarding the timeout theory, the ReportDownloader won't 
>> 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Ron,

The engineering team is still digging into this. I'll be sure to update 
this thread as soon as I have more information.

In the meantime, please retry the requests as Dorian suggested earlier.

Thanks,
Josh, AdWords API Team

On Wednesday, May 16, 2018 at 4:34:19 PM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> are there any updates on this topic? We are eagerly awaiting your response 
> on this one.
>
> Best Regards,
> Ron
>
> Am Freitag, 4. Mai 2018 21:18:47 UTC+2 schrieb Josh Radcliff (AdWords API 
> Team):
>>
>> Hi Dorian,
>>
>> Tracking down the root cause is proving quite challenging, so I don't 
>> have any news to report just yet. In the meantime, retrying failed requests 
>> (provided you're confident the request is valid) is a good approach.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, May 4, 2018 at 7:32:45 AM UTC-4, Dorian Kind wrote:
>>>
>>> Hi Josh,
>>>
>>> any updates on this topic? Can we just retry downloads that fail with 
>>> this specific error condition (400 HTTP status code and no response 
>>> content) for the time being?
>>>
>>> Thanks for your feedback and best regards,
>>> Dorian
>>>
>>> On Monday, 23 April 2018 14:52:50 UTC+2, Josh Radcliff (AdWords API 
>>> Team) wrote:

 Hi Ron,

 Thanks for getting back to me. I think we have enough examples now to 
 track this down. The eng team is making progress, but I don't have any 
 updates to report just yet. I'll reply back as soon as I have more info.

 Cheers,
 Josh, AdWords API Team

 On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>
> Taking into account the daylight savings we currently have UTC+2.
> Concerning the 502 unfortionately I don't have the logs at hand any 
> more -- but what I remember was an 502 which resulted in a 400 in our 
> usage 
> of the library.
>
> Best Regards,
> Ron
>
> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff 
> (AdWords API Team):
>>
>> Also, I forgot to ask: is that timestamp in CST?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi Ron,
>>>
>>> I'm a little perplexed by the most recent example. I see it shows 
>>> both:
>>>
>>> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad 
>>> Gateway
>>>
>>> and:
>>>
>>> Caused by: HTTP Response Code: *400*
>>>
>>> Was that a bad copy/paste, or are you actually seeing both 502 and 
>>> 400 mentioned within the same error?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling 
>>> wrote:

 After adding some more logging, another example that results in a 
 400 on our side:


 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
 Service: reportdownload Method: POST clientCustomerId: XXX 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: 
 502: 
 Bad Gateway
 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
 request:
 accept-encoding: [gzip]
 authorization: REDACTED
 user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
 maven, ReportDownloader)]
 developertoken: REDACTED
 clientcustomerid: XXX
 includezeroimpressions: false

 Content:
 __rdquery: SELECT Conversions,ConversionValue FROM 
 SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
 20180316,20180415
 __fmt: XML

 Caused by: HTTP Response Code: 400 at 
 com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)

 Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff 
 (AdWords API Team):
>
> Hi Ron,
>
> Sorry, I'm still having trouble locating those requests in our 
> logs. Would you mind sending over the customer ID where your 
> developer 
> token is registered? You can send it only to me by clicking *Reply 
> privately to author*.
>
> Regarding the timeout theory, the ReportDownloader won't 
> automatically retry requests. However, if you think timeouts are the 
> root 
> cause here, you can adjust the timeout for report downloads 
> programmatically or in your *ads.properties* file. Check out this 
> section of the ads.properties file 
> 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Ronald Findling]

Hi Josh,

are there any updates on this topic? We are eagerly awaiting your response 
on this one.

Best Regards,
Ron

Am Freitag, 4. Mai 2018 21:18:47 UTC+2 schrieb Josh Radcliff (AdWords API 
Team):
>
> Hi Dorian,
>
> Tracking down the root cause is proving quite challenging, so I don't have 
> any news to report just yet. In the meantime, retrying failed requests 
> (provided you're confident the request is valid) is a good approach.
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, May 4, 2018 at 7:32:45 AM UTC-4, Dorian Kind wrote:
>>
>> Hi Josh,
>>
>> any updates on this topic? Can we just retry downloads that fail with 
>> this specific error condition (400 HTTP status code and no response 
>> content) for the time being?
>>
>> Thanks for your feedback and best regards,
>> Dorian
>>
>> On Monday, 23 April 2018 14:52:50 UTC+2, Josh Radcliff (AdWords API Team) 
>> wrote:
>>>
>>> Hi Ron,
>>>
>>> Thanks for getting back to me. I think we have enough examples now to 
>>> track this down. The eng team is making progress, but I don't have any 
>>> updates to report just yet. I'll reply back as soon as I have more info.
>>>
>>> Cheers,
>>> Josh, AdWords API Team
>>>
>>> On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:

 Taking into account the daylight savings we currently have UTC+2.
 Concerning the 502 unfortionately I don't have the logs at hand any 
 more -- but what I remember was an 502 which resulted in a 400 in our 
 usage 
 of the library.

 Best Regards,
 Ron

 Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff (AdWords 
 API Team):
>
> Also, I forgot to ask: is that timestamp in CST?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Ron,
>>
>> I'm a little perplexed by the most recent example. I see it shows 
>> both:
>>
>> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad 
>> Gateway
>>
>> and:
>>
>> Caused by: HTTP Response Code: *400*
>>
>> Was that a bad copy/paste, or are you actually seeing both 502 and 
>> 400 mentioned within the same error?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>>>
>>> After adding some more logging, another example that results in a 
>>> 400 on our side:
>>>
>>>
>>> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
>>> Service: reportdownload Method: POST clientCustomerId: XXX 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: 
>>> 502: 
>>> Bad Gateway
>>> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
>>> request:
>>> accept-encoding: [gzip]
>>> authorization: REDACTED
>>> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
>>> maven, ReportDownloader)]
>>> developertoken: REDACTED
>>> clientcustomerid: XXX
>>> includezeroimpressions: false
>>>
>>> Content:
>>> __rdquery: SELECT Conversions,ConversionValue FROM 
>>> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
>>> 20180316,20180415
>>> __fmt: XML
>>>
>>> Caused by: HTTP Response Code: 400 at 
>>> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>>>
>>> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff 
>>> (AdWords API Team):

 Hi Ron,

 Sorry, I'm still having trouble locating those requests in our 
 logs. Would you mind sending over the customer ID where your developer 
 token is registered? You can send it only to me by clicking *Reply 
 privately to author*.

 Regarding the timeout theory, the ReportDownloader won't 
 automatically retry requests. However, if you think timeouts are the 
 root 
 cause here, you can adjust the timeout for report downloads 
 programmatically or in your *ads.properties* file. Check out this 
 section of the ads.properties file 
 
  for 
 details.

 Thanks,
 Josh, AdWords API Team

 On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling 
 wrote:
>
> Hi Josh,
>
> I checked the request data that I provided you and they are 
> exactly what I can see in my logs. Maybe I should 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Dorian,

Tracking down the root cause is proving quite challenging, so I don't have 
any news to report just yet. In the meantime, retrying failed requests 
(provided you're confident the request is valid) is a good approach.

Thanks,
Josh, AdWords API Team

On Friday, May 4, 2018 at 7:32:45 AM UTC-4, Dorian Kind wrote:
>
> Hi Josh,
>
> any updates on this topic? Can we just retry downloads that fail with this 
> specific error condition (400 HTTP status code and no response content) for 
> the time being?
>
> Thanks for your feedback and best regards,
> Dorian
>
> On Monday, 23 April 2018 14:52:50 UTC+2, Josh Radcliff (AdWords API Team) 
> wrote:
>>
>> Hi Ron,
>>
>> Thanks for getting back to me. I think we have enough examples now to 
>> track this down. The eng team is making progress, but I don't have any 
>> updates to report just yet. I'll reply back as soon as I have more info.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>>>
>>> Taking into account the daylight savings we currently have UTC+2.
>>> Concerning the 502 unfortionately I don't have the logs at hand any more 
>>> -- but what I remember was an 502 which resulted in a 400 in our usage of 
>>> the library.
>>>
>>> Best Regards,
>>> Ron
>>>
>>> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff (AdWords 
>>> API Team):

 Also, I forgot to ask: is that timestamp in CST?

 Thanks,
 Josh, AdWords API Team

 On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords 
 API Team) wrote:
>
> Hi Ron,
>
> I'm a little perplexed by the most recent example. I see it shows both:
>
> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad 
> Gateway
>
> and:
>
> Caused by: HTTP Response Code: *400*
>
> Was that a bad copy/paste, or are you actually seeing both 502 and 400 
> mentioned within the same error?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>>
>> After adding some more logging, another example that results in a 400 
>> on our side:
>>
>>
>> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
>> Service: reportdownload Method: POST clientCustomerId: XXX 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: 502: 
>> Bad Gateway
>> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
>> request:
>> accept-encoding: [gzip]
>> authorization: REDACTED
>> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
>> maven, ReportDownloader)]
>> developertoken: REDACTED
>> clientcustomerid: XXX
>> includezeroimpressions: false
>>
>> Content:
>> __rdquery: SELECT Conversions,ConversionValue FROM 
>> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
>> 20180316,20180415
>> __fmt: XML
>>
>> Caused by: HTTP Response Code: 400 at 
>> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>>
>> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff 
>> (AdWords API Team):
>>>
>>> Hi Ron,
>>>
>>> Sorry, I'm still having trouble locating those requests in our logs. 
>>> Would you mind sending over the customer ID where your developer token 
>>> is 
>>> registered? You can send it only to me by clicking *Reply privately 
>>> to author*.
>>>
>>> Regarding the timeout theory, the ReportDownloader won't 
>>> automatically retry requests. However, if you think timeouts are the 
>>> root 
>>> cause here, you can adjust the timeout for report downloads 
>>> programmatically or in your *ads.properties* file. Check out this 
>>> section of the ads.properties file 
>>> 
>>>  for 
>>> details.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling 
>>> wrote:

 Hi Josh,

 I checked the request data that I provided you and they are exactly 
 what I can see in my logs. Maybe I should mention that the provided 
 time is 
 the time at which the request failed not when it was sent to your 
 servers 
 (that time is ~30-40 seconds before).

 Concerning the thread-safety recommendations I'm sure that the 
 ReportDownloader and its Session are not used in multiple threads in 
 our 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Dorian Kind]

Hi Josh,

any updates on this topic? Can we just retry downloads that fail with this 
specific error condition (400 HTTP status code and no response content) for 
the time being?

Thanks for your feedback and best regards,
Dorian

On Monday, 23 April 2018 14:52:50 UTC+2, Josh Radcliff (AdWords API Team) 
wrote:
>
> Hi Ron,
>
> Thanks for getting back to me. I think we have enough examples now to 
> track this down. The eng team is making progress, but I don't have any 
> updates to report just yet. I'll reply back as soon as I have more info.
>
> Cheers,
> Josh, AdWords API Team
>
> On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>>
>> Taking into account the daylight savings we currently have UTC+2.
>> Concerning the 502 unfortionately I don't have the logs at hand any more 
>> -- but what I remember was an 502 which resulted in a 400 in our usage of 
>> the library.
>>
>> Best Regards,
>> Ron
>>
>> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Also, I forgot to ask: is that timestamp in CST?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords 
>>> API Team) wrote:

 Hi Ron,

 I'm a little perplexed by the most recent example. I see it shows both:

 com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad 
 Gateway

 and:

 Caused by: HTTP Response Code: *400*

 Was that a bad copy/paste, or are you actually seeing both 502 and 400 
 mentioned within the same error?

 Thanks,
 Josh, AdWords API Team

 On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>
> After adding some more logging, another example that results in a 400 
> on our side:
>
>
> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
> Service: reportdownload Method: POST clientCustomerId: XXX 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: 502: 
> Bad Gateway
> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
> request:
> accept-encoding: [gzip]
> authorization: REDACTED
> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
> maven, ReportDownloader)]
> developertoken: REDACTED
> clientcustomerid: XXX
> includezeroimpressions: false
>
> Content:
> __rdquery: SELECT Conversions,ConversionValue FROM 
> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
> 20180316,20180415
> __fmt: XML
>
> Caused by: HTTP Response Code: 400 at 
> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>
> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff 
> (AdWords API Team):
>>
>> Hi Ron,
>>
>> Sorry, I'm still having trouble locating those requests in our logs. 
>> Would you mind sending over the customer ID where your developer token 
>> is 
>> registered? You can send it only to me by clicking *Reply privately 
>> to author*.
>>
>> Regarding the timeout theory, the ReportDownloader won't 
>> automatically retry requests. However, if you think timeouts are the 
>> root 
>> cause here, you can adjust the timeout for report downloads 
>> programmatically or in your *ads.properties* file. Check out this 
>> section of the ads.properties file 
>> 
>>  for 
>> details.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling 
>> wrote:
>>>
>>> Hi Josh,
>>>
>>> I checked the request data that I provided you and they are exactly 
>>> what I can see in my logs. Maybe I should mention that the provided 
>>> time is 
>>> the time at which the request failed not when it was sent to your 
>>> servers 
>>> (that time is ~30-40 seconds before).
>>>
>>> Concerning the thread-safety recommendations I'm sure that the 
>>> ReportDownloader and its Session are not used in multiple threads in 
>>> our 
>>> code.
>>>
>>> Further information: 
>>> Checking our errors I found an interesting pattern, failing requests 
>>> always take at least 30 seconds (usually 30-31) while successful ones 
>>> are 
>>> most likely to be around 1 second.
>>>
>>> Maybe a stupid thought but could it be a something like the 
>>> java-library timing out after 30 seconds and retrying using the 
>>> provided 
>>> 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ron,

Thanks for getting back to me. I think we have enough examples now to track 
this down. The eng team is making progress, but I don't have any updates to 
report just yet. I'll reply back as soon as I have more info.

Cheers,
Josh, AdWords API Team

On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>
> Taking into account the daylight savings we currently have UTC+2.
> Concerning the 502 unfortionately I don't have the logs at hand any more 
> -- but what I remember was an 502 which resulted in a 400 in our usage of 
> the library.
>
> Best Regards,
> Ron
>
> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff (AdWords 
> API Team):
>>
>> Also, I forgot to ask: is that timestamp in CST?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Ron,
>>>
>>> I'm a little perplexed by the most recent example. I see it shows both:
>>>
>>> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad Gateway
>>>
>>> and:
>>>
>>> Caused by: HTTP Response Code: *400*
>>>
>>> Was that a bad copy/paste, or are you actually seeing both 502 and 400 
>>> mentioned within the same error?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:

 After adding some more logging, another example that results in a 400 
 on our side:


 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
 Service: reportdownload Method: POST clientCustomerId: XXX 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: 502: 
 Bad Gateway
 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
 request:
 accept-encoding: [gzip]
 authorization: REDACTED
 user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
 maven, ReportDownloader)]
 developertoken: REDACTED
 clientcustomerid: XXX
 includezeroimpressions: false

 Content:
 __rdquery: SELECT Conversions,ConversionValue FROM 
 SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
 20180316,20180415
 __fmt: XML

 Caused by: HTTP Response Code: 400 at 
 com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)

 Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff (AdWords 
 API Team):
>
> Hi Ron,
>
> Sorry, I'm still having trouble locating those requests in our logs. 
> Would you mind sending over the customer ID where your developer token is 
> registered? You can send it only to me by clicking *Reply privately 
> to author*.
>
> Regarding the timeout theory, the ReportDownloader won't automatically 
> retry requests. However, if you think timeouts are the root cause here, 
> you 
> can adjust the timeout for report downloads programmatically or in your 
> *ads.properties* file. Check out this section of the ads.properties 
> file 
> 
>  for 
> details.
>
> Thanks,
> Josh, AdWords API Team
>
> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling 
> wrote:
>>
>> Hi Josh,
>>
>> I checked the request data that I provided you and they are exactly 
>> what I can see in my logs. Maybe I should mention that the provided time 
>> is 
>> the time at which the request failed not when it was sent to your 
>> servers 
>> (that time is ~30-40 seconds before).
>>
>> Concerning the thread-safety recommendations I'm sure that the 
>> ReportDownloader and its Session are not used in multiple threads in our 
>> code.
>>
>> Further information: 
>> Checking our errors I found an interesting pattern, failing requests 
>> always take at least 30 seconds (usually 30-31) while successful ones 
>> are 
>> most likely to be around 1 second.
>>
>> Maybe a stupid thought but could it be a something like the 
>> java-library timing out after 30 seconds and retrying using the provided 
>> session/ReportDownloader again which then violates the threadSafety and 
>> results in invalid requests?
>>
>> Best Regards,
>> Ron
>>
>>
>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff 
>> (AdWords API Team):
>>>
>>> Hi Ronald,
>>>
>>> I searched the logs on our side and could not find either of those 
>>> requests. Are you sure that they were submitted for the account ID you 
>>> mentioned?
>>>
>>> By the way, 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Ronald Findling]

Taking into account the daylight savings we currently have UTC+2.
Concerning the 502 unfortionately I don't have the logs at hand any more -- 
but what I remember was an 502 which resulted in a 400 in our usage of the 
library.

Best Regards,
Ron

Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff (AdWords API 
Team):
>
> Also, I forgot to ask: is that timestamp in CST?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Ron,
>>
>> I'm a little perplexed by the most recent example. I see it shows both:
>>
>> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad Gateway
>>
>> and:
>>
>> Caused by: HTTP Response Code: *400*
>>
>> Was that a bad copy/paste, or are you actually seeing both 502 and 400 
>> mentioned within the same error?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>>>
>>> After adding some more logging, another example that results in a 400 on 
>>> our side:
>>>
>>>
>>> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
>>> Service: reportdownload Method: POST clientCustomerId: XXX 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: 502: 
>>> Bad Gateway
>>> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
>>> request:
>>> accept-encoding: [gzip]
>>> authorization: REDACTED
>>> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, maven, 
>>> ReportDownloader)]
>>> developertoken: REDACTED
>>> clientcustomerid: XXX
>>> includezeroimpressions: false
>>>
>>> Content:
>>> __rdquery: SELECT Conversions,ConversionValue FROM 
>>> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
>>> 20180316,20180415
>>> __fmt: XML
>>>
>>> Caused by: HTTP Response Code: 400 at 
>>> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>>>
>>> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff (AdWords 
>>> API Team):

 Hi Ron,

 Sorry, I'm still having trouble locating those requests in our logs. 
 Would you mind sending over the customer ID where your developer token is 
 registered? You can send it only to me by clicking *Reply privately to 
 author*.

 Regarding the timeout theory, the ReportDownloader won't automatically 
 retry requests. However, if you think timeouts are the root cause here, 
 you 
 can adjust the timeout for report downloads programmatically or in your 
 *ads.properties* file. Check out this section of the ads.properties 
 file 
 
  for 
 details.

 Thanks,
 Josh, AdWords API Team

 On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> I checked the request data that I provided you and they are exactly 
> what I can see in my logs. Maybe I should mention that the provided time 
> is 
> the time at which the request failed not when it was sent to your servers 
> (that time is ~30-40 seconds before).
>
> Concerning the thread-safety recommendations I'm sure that the 
> ReportDownloader and its Session are not used in multiple threads in our 
> code.
>
> Further information: 
> Checking our errors I found an interesting pattern, failing requests 
> always take at least 30 seconds (usually 30-31) while successful ones are 
> most likely to be around 1 second.
>
> Maybe a stupid thought but could it be a something like the 
> java-library timing out after 30 seconds and retrying using the provided 
> session/ReportDownloader again which then violates the threadSafety and 
> results in invalid requests?
>
> Best Regards,
> Ron
>
>
> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff 
> (AdWords API Team):
>>
>> Hi Ronald,
>>
>> I searched the logs on our side and could not find either of those 
>> requests. Are you sure that they were submitted for the account ID you 
>> mentioned?
>>
>> By the way, did you check if you're adhering to the thread safety 
>> guidelines I mentioned earlier? I just want to make sure we can rule 
>> that 
>> out as a possible cause of the errors.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>>>
>>> Hi Josh,
>>>
>>> thx for the hints.
>>> Concerning the requested information I can give you 2 identical 
>>> request where one 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Also, I forgot to ask: is that timestamp in CST?

Thanks,
Josh, AdWords API Team

On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Ron,
>
> I'm a little perplexed by the most recent example. I see it shows both:
>
> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad Gateway
>
> and:
>
> Caused by: HTTP Response Code: *400*
>
> Was that a bad copy/paste, or are you actually seeing both 502 and 400 
> mentioned within the same error?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>>
>> After adding some more logging, another example that results in a 400 on 
>> our side:
>>
>>
>> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
>> Service: reportdownload Method: POST clientCustomerId: XXX 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: 502: 
>> Bad Gateway
>> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
>> request:
>> accept-encoding: [gzip]
>> authorization: REDACTED
>> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, maven, 
>> ReportDownloader)]
>> developertoken: REDACTED
>> clientcustomerid: XXX
>> includezeroimpressions: false
>>
>> Content:
>> __rdquery: SELECT Conversions,ConversionValue FROM 
>> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
>> 20180316,20180415
>> __fmt: XML
>>
>> Caused by: HTTP Response Code: 400 at 
>> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>>
>> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Hi Ron,
>>>
>>> Sorry, I'm still having trouble locating those requests in our logs. 
>>> Would you mind sending over the customer ID where your developer token is 
>>> registered? You can send it only to me by clicking *Reply privately to 
>>> author*.
>>>
>>> Regarding the timeout theory, the ReportDownloader won't automatically 
>>> retry requests. However, if you think timeouts are the root cause here, you 
>>> can adjust the timeout for report downloads programmatically or in your 
>>> *ads.properties* file. Check out this section of the ads.properties file 
>>> 
>>>  for 
>>> details.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:

 Hi Josh,

 I checked the request data that I provided you and they are exactly 
 what I can see in my logs. Maybe I should mention that the provided time 
 is 
 the time at which the request failed not when it was sent to your servers 
 (that time is ~30-40 seconds before).

 Concerning the thread-safety recommendations I'm sure that the 
 ReportDownloader and its Session are not used in multiple threads in our 
 code.

 Further information: 
 Checking our errors I found an interesting pattern, failing requests 
 always take at least 30 seconds (usually 30-31) while successful ones are 
 most likely to be around 1 second.

 Maybe a stupid thought but could it be a something like the 
 java-library timing out after 30 seconds and retrying using the provided 
 session/ReportDownloader again which then violates the threadSafety and 
 results in invalid requests?

 Best Regards,
 Ron


 Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff 
 (AdWords API Team):
>
> Hi Ronald,
>
> I searched the logs on our side and could not find either of those 
> requests. Are you sure that they were submitted for the account ID you 
> mentioned?
>
> By the way, did you check if you're adhering to the thread safety 
> guidelines I mentioned earlier? I just want to make sure we can rule that 
> out as a possible cause of the errors.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>>
>> Hi Josh,
>>
>> thx for the hints.
>> Concerning the requested information I can give you 2 identical 
>> request where one succeeded and the other one failed with a 400 as shown 
>> in 
>> my last message.
>>
>> failed:
>> time: 27.03.18 01:06:08 CEST
>> googleAdwordsAccountId: 685-366-2732
>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
>> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>>
>> succeeded:
>> time: 27.03.18 03:06:30 CEST
>> googleAdwordsAccountId: 685-366-2732
>> SELECT Conversions,ConversionValue FROM 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ron,

I'm a little perplexed by the most recent example. I see it shows both:

com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad Gateway

and:

Caused by: HTTP Response Code: *400*

Was that a bad copy/paste, or are you actually seeing both 502 and 400 
mentioned within the same error?

Thanks,
Josh, AdWords API Team

On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>
> After adding some more logging, another example that results in a 400 on 
> our side:
>
>
> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: Service: 
> reportdownload Method: POST clientCustomerId: XXX 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: 502: 
> Bad Gateway
> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
> request:
> accept-encoding: [gzip]
> authorization: REDACTED
> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, maven, 
> ReportDownloader)]
> developertoken: REDACTED
> clientcustomerid: XXX
> includezeroimpressions: false
>
> Content:
> __rdquery: SELECT Conversions,ConversionValue FROM 
> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
> 20180316,20180415
> __fmt: XML
>
> Caused by: HTTP Response Code: 400 at 
> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>
> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff (AdWords 
> API Team):
>>
>> Hi Ron,
>>
>> Sorry, I'm still having trouble locating those requests in our logs. 
>> Would you mind sending over the customer ID where your developer token is 
>> registered? You can send it only to me by clicking *Reply privately to 
>> author*.
>>
>> Regarding the timeout theory, the ReportDownloader won't automatically 
>> retry requests. However, if you think timeouts are the root cause here, you 
>> can adjust the timeout for report downloads programmatically or in your 
>> *ads.properties* file. Check out this section of the ads.properties file 
>> 
>>  for 
>> details.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>>
>>> Hi Josh,
>>>
>>> I checked the request data that I provided you and they are exactly what 
>>> I can see in my logs. Maybe I should mention that the provided time is the 
>>> time at which the request failed not when it was sent to your servers (that 
>>> time is ~30-40 seconds before).
>>>
>>> Concerning the thread-safety recommendations I'm sure that the 
>>> ReportDownloader and its Session are not used in multiple threads in our 
>>> code.
>>>
>>> Further information: 
>>> Checking our errors I found an interesting pattern, failing requests 
>>> always take at least 30 seconds (usually 30-31) while successful ones are 
>>> most likely to be around 1 second.
>>>
>>> Maybe a stupid thought but could it be a something like the java-library 
>>> timing out after 30 seconds and retrying using the provided 
>>> session/ReportDownloader again which then violates the threadSafety and 
>>> results in invalid requests?
>>>
>>> Best Regards,
>>> Ron
>>>
>>>
>>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
>>> API Team):

 Hi Ronald,

 I searched the logs on our side and could not find either of those 
 requests. Are you sure that they were submitted for the account ID you 
 mentioned?

 By the way, did you check if you're adhering to the thread safety 
 guidelines I mentioned earlier? I just want to make sure we can rule that 
 out as a possible cause of the errors.

 Thanks,
 Josh, AdWords API Team

 On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> thx for the hints.
> Concerning the requested information I can give you 2 identical 
> request where one succeeded and the other one failed with a 400 as shown 
> in 
> my last message.
>
> failed:
> time: 27.03.18 01:06:08 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> succeeded:
> time: 27.03.18 03:06:30 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> Best Regards, Ron
>
> Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff 
> (AdWords API Team):
>>
>> Hi Raneen,
>>
>> From our logs, it appears that your requests are most 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Ronald Findling]

After adding some more logging, another example that results in a 400 on 
our side:


19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: Service: 
reportdownload Method: POST clientCustomerId: XXX 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: 502: 
Bad Gateway
2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP request:
accept-encoding: [gzip]
authorization: REDACTED
user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, maven, 
ReportDownloader)]
developertoken: REDACTED
clientcustomerid: XXX
includezeroimpressions: false

Content:
__rdquery: SELECT Conversions,ConversionValue FROM 
SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
20180316,20180415
__fmt: XML

Caused by: HTTP Response Code: 400 at 
com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)

Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff (AdWords API 
Team):
>
> Hi Ron,
>
> Sorry, I'm still having trouble locating those requests in our logs. Would 
> you mind sending over the customer ID where your developer token is 
> registered? You can send it only to me by clicking *Reply privately to 
> author*.
>
> Regarding the timeout theory, the ReportDownloader won't automatically 
> retry requests. However, if you think timeouts are the root cause here, you 
> can adjust the timeout for report downloads programmatically or in your 
> *ads.properties* file. Check out this section of the ads.properties file 
> 
>  for 
> details.
>
> Thanks,
> Josh, AdWords API Team
>
> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>
>> Hi Josh,
>>
>> I checked the request data that I provided you and they are exactly what 
>> I can see in my logs. Maybe I should mention that the provided time is the 
>> time at which the request failed not when it was sent to your servers (that 
>> time is ~30-40 seconds before).
>>
>> Concerning the thread-safety recommendations I'm sure that the 
>> ReportDownloader and its Session are not used in multiple threads in our 
>> code.
>>
>> Further information: 
>> Checking our errors I found an interesting pattern, failing requests 
>> always take at least 30 seconds (usually 30-31) while successful ones are 
>> most likely to be around 1 second.
>>
>> Maybe a stupid thought but could it be a something like the java-library 
>> timing out after 30 seconds and retrying using the provided 
>> session/ReportDownloader again which then violates the threadSafety and 
>> results in invalid requests?
>>
>> Best Regards,
>> Ron
>>
>>
>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Hi Ronald,
>>>
>>> I searched the logs on our side and could not find either of those 
>>> requests. Are you sure that they were submitted for the account ID you 
>>> mentioned?
>>>
>>> By the way, did you check if you're adhering to the thread safety 
>>> guidelines I mentioned earlier? I just want to make sure we can rule that 
>>> out as a possible cause of the errors.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:

 Hi Josh,

 thx for the hints.
 Concerning the requested information I can give you 2 identical request 
 where one succeeded and the other one failed with a 400 as shown in my 
 last 
 message.

 failed:
 time: 27.03.18 01:06:08 CEST
 googleAdwordsAccountId: 685-366-2732
 SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
 WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;

 succeeded:
 time: 27.03.18 03:06:30 CEST
 googleAdwordsAccountId: 685-366-2732
 SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
 WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;

 Best Regards, Ron

 Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff 
 (AdWords API Team):
>
> Hi Raneen,
>
> From our logs, it appears that your requests are most frequently 
> failing with the following errors:
>
>- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
>- AuthorizationError.USER_PERMISSION_DENIED
>- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
>
> Could you share a report request that failed, with any sensitive 
> information removed (developer token, OAuth access token, etc.)?
>
> Also, I see that you are using the client library for Java. Are you 
> adhering to the thread-safety recommendations 
> 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Ronald Findling]

After adding some more logging, another example that results in a 400 on 
our side:


19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: Service: 
reportdownload Method: POST clientCustomerId: 858-429-0765 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: 502: 
Bad Gateway
2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP request:
accept-encoding: [gzip]
authorization: REDACTED
user-agent: [smeco (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, maven, 
ReportDownloader)]
developertoken: REDACTED
clientcustomerid: 858-429-0765
includezeroimpressions: false

Content:
__rdquery: SELECT Conversions,ConversionValue FROM 
SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
20180316,20180415
__fmt: XML

Caused by: HTTP Response Code: 400 at 
com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/13b5f9e7-1899-442f-aaea-fc7bcdfc490f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Thanks for providing the customer IDs and timestamps of the failed 
requests. I've passed those along to the reporting team for investigation 
and asked for an update.

Cheers,
Josh, AdWords API Team

On Thursday, April 12, 2018 at 6:11:34 AM UTC-4, Zweitze wrote:
>
> This topic was somehow below my radar, but I occasionally get this too. See 
> here 
>  
> for recent logs and the response headers that AdWordsAPI sent.
> This error occurred on:
> Dec 22
> Dec 25 (3 times)
> Dec 31
> Jan 1
> Jan 12
> Feb 1
> Feb 6 (2 times)
> Mar 17 (3 times)
> Mar 18
> Mar 23
> Mar 24
> Mar 25
> Mar 26
> Mar 30
> Apr 1
> Apr 3
> Apr 11 (3 times)
> (@Google: I have requests and response headers for each instance).
> We retrieve between 1,000 and 20,000 reports daily. Problems occur on 
> different report types, on different accounts - I can't find a pattern on 
> that.
>
> Like Dorian I wonder how to deal with that error, as a 400-error means a 
> serious error by the client.
>
> On Tuesday, April 3, 2018 at 5:12:12 PM UTC+2, Dorian Kind wrote:
>>
>> Hi all,
>>
>> I thought I posted previously in this thread, but it looks like my 
>> message has been deleted. I just wanted to chime in that we've also been 
>> seeing these sporadic report failures that return a HTTP 400 status code 
>> and no reponse content. They don't seem to be reproducible, from what we 
>> can tell and are most likely not the result of an expired OAuth token or a 
>> malformed report definition as both of these cases give detailed error 
>> messages.
>> We don't feel comfortable automatically retrying report download requests 
>> for error codes below 500, so it'd be great if the Adwords team could shed 
>> some light on the issue.
>>
>> Thanks and best regards,
>> Dorian
>>
>> On Friday, 30 March 2018 15:15:38 UTC+2, Josh Radcliff (AdWords API Team) 
>> wrote:
>>>
>>> Hi Ron,
>>>
>>> Sorry, I'm still having trouble locating those requests in our logs. 
>>> Would you mind sending over the customer ID where your developer token is 
>>> registered? You can send it only to me by clicking *Reply privately to 
>>> author*.
>>>
>>> Regarding the timeout theory, the ReportDownloader won't automatically 
>>> retry requests. However, if you think timeouts are the root cause here, you 
>>> can adjust the timeout for report downloads programmatically or in your 
>>> *ads.properties* file. Check out this section of the ads.properties file 
>>> 
>>>  for 
>>> details.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:

 Hi Josh,

 I checked the request data that I provided you and they are exactly 
 what I can see in my logs. Maybe I should mention that the provided time 
 is 
 the time at which the request failed not when it was sent to your servers 
 (that time is ~30-40 seconds before).

 Concerning the thread-safety recommendations I'm sure that the 
 ReportDownloader and its Session are not used in multiple threads in our 
 code.

 Further information: 
 Checking our errors I found an interesting pattern, failing requests 
 always take at least 30 seconds (usually 30-31) while successful ones are 
 most likely to be around 1 second.

 Maybe a stupid thought but could it be a something like the 
 java-library timing out after 30 seconds and retrying using the provided 
 session/ReportDownloader again which then violates the threadSafety and 
 results in invalid requests?

 Best Regards,
 Ron


 Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff 
 (AdWords API Team):
>
> Hi Ronald,
>
> I searched the logs on our side and could not find either of those 
> requests. Are you sure that they were submitted for the account ID you 
> mentioned?
>
> By the way, did you check if you're adhering to the thread safety 
> guidelines I mentioned earlier? I just want to make sure we can rule that 
> out as a possible cause of the errors.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>>
>> Hi Josh,
>>
>> thx for the hints.
>> Concerning the requested information I can give you 2 identical 
>> request where one succeeded and the other one failed with a 400 as shown 
>> in 
>> my last message.
>>
>> failed:
>> time: 27.03.18 01:06:08 CEST
>> googleAdwordsAccountId: 685-366-2732
>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
>> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>>
>> succeeded:
>> time: 27.03.18 03:06:30 CEST
>> googleAdwordsAccountId: 685-366-2732

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Zweitze]

This topic was somehow below my radar, but I occasionally get this too. See 
here  
for recent logs and the response headers that AdWordsAPI sent.
This error occurred on:
Dec 22
Dec 25 (3 times)
Dec 31
Jan 1
Jan 12
Feb 1
Feb 6 (2 times)
Mar 17 (3 times)
Mar 18
Mar 23
Mar 24
Mar 25
Mar 26
Mar 30
Apr 1
Apr 3
Apr 11 (3 times)
(@Google: I have requests and response headers for each instance).
We retrieve between 1,000 and 20,000 reports daily. Problems occur on 
different report types, on different accounts - I can't find a pattern on 
that.

Like Dorian I wonder how to deal with that error, as a 400-error means a 
serious error by the client.

On Tuesday, April 3, 2018 at 5:12:12 PM UTC+2, Dorian Kind wrote:
>
> Hi all,
>
> I thought I posted previously in this thread, but it looks like my message 
> has been deleted. I just wanted to chime in that we've also been seeing 
> these sporadic report failures that return a HTTP 400 status code and no 
> reponse content. They don't seem to be reproducible, from what we can tell 
> and are most likely not the result of an expired OAuth token or a malformed 
> report definition as both of these cases give detailed error messages.
> We don't feel comfortable automatically retrying report download requests 
> for error codes below 500, so it'd be great if the Adwords team could shed 
> some light on the issue.
>
> Thanks and best regards,
> Dorian
>
> On Friday, 30 March 2018 15:15:38 UTC+2, Josh Radcliff (AdWords API Team) 
> wrote:
>>
>> Hi Ron,
>>
>> Sorry, I'm still having trouble locating those requests in our logs. 
>> Would you mind sending over the customer ID where your developer token is 
>> registered? You can send it only to me by clicking *Reply privately to 
>> author*.
>>
>> Regarding the timeout theory, the ReportDownloader won't automatically 
>> retry requests. However, if you think timeouts are the root cause here, you 
>> can adjust the timeout for report downloads programmatically or in your 
>> *ads.properties* file. Check out this section of the ads.properties file 
>> 
>>  for 
>> details.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>>
>>> Hi Josh,
>>>
>>> I checked the request data that I provided you and they are exactly what 
>>> I can see in my logs. Maybe I should mention that the provided time is the 
>>> time at which the request failed not when it was sent to your servers (that 
>>> time is ~30-40 seconds before).
>>>
>>> Concerning the thread-safety recommendations I'm sure that the 
>>> ReportDownloader and its Session are not used in multiple threads in our 
>>> code.
>>>
>>> Further information: 
>>> Checking our errors I found an interesting pattern, failing requests 
>>> always take at least 30 seconds (usually 30-31) while successful ones are 
>>> most likely to be around 1 second.
>>>
>>> Maybe a stupid thought but could it be a something like the java-library 
>>> timing out after 30 seconds and retrying using the provided 
>>> session/ReportDownloader again which then violates the threadSafety and 
>>> results in invalid requests?
>>>
>>> Best Regards,
>>> Ron
>>>
>>>
>>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
>>> API Team):

 Hi Ronald,

 I searched the logs on our side and could not find either of those 
 requests. Are you sure that they were submitted for the account ID you 
 mentioned?

 By the way, did you check if you're adhering to the thread safety 
 guidelines I mentioned earlier? I just want to make sure we can rule that 
 out as a possible cause of the errors.

 Thanks,
 Josh, AdWords API Team

 On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> thx for the hints.
> Concerning the requested information I can give you 2 identical 
> request where one succeeded and the other one failed with a 400 as shown 
> in 
> my last message.
>
> failed:
> time: 27.03.18 01:06:08 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> succeeded:
> time: 27.03.18 03:06:30 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> Best Regards, Ron
>
> Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff 
> (AdWords API Team):
>>
>> Hi Raneen,
>>
>> From our logs, it appears that your requests are most frequently 
>> failing with the following errors:
>>
>>- 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi all,

Thanks for letting us know about these errors. I'm following up with our 
reporting team and will post back here when I have an update.

Cheers,
Josh, AdWords API Team

On Tuesday, April 3, 2018 at 11:12:12 AM UTC-4, Dorian Kind wrote:
>
> Hi all,
>
> I thought I posted previously in this thread, but it looks like my message 
> has been deleted. I just wanted to chime in that we've also been seeing 
> these sporadic report failures that return a HTTP 400 status code and no 
> reponse content. They don't seem to be reproducible, from what we can tell 
> and are most likely not the result of an expired OAuth token or a malformed 
> report definition as both of these cases give detailed error messages.
> We don't feel comfortable automatically retrying report download requests 
> for error codes below 500, so it'd be great if the Adwords team could shed 
> some light on the issue.
>
> Thanks and best regards,
> Dorian
>
> On Friday, 30 March 2018 15:15:38 UTC+2, Josh Radcliff (AdWords API Team) 
> wrote:
>>
>> Hi Ron,
>>
>> Sorry, I'm still having trouble locating those requests in our logs. 
>> Would you mind sending over the customer ID where your developer token is 
>> registered? You can send it only to me by clicking *Reply privately to 
>> author*.
>>
>> Regarding the timeout theory, the ReportDownloader won't automatically 
>> retry requests. However, if you think timeouts are the root cause here, you 
>> can adjust the timeout for report downloads programmatically or in your 
>> *ads.properties* file. Check out this section of the ads.properties file 
>> 
>>  for 
>> details.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>>
>>> Hi Josh,
>>>
>>> I checked the request data that I provided you and they are exactly what 
>>> I can see in my logs. Maybe I should mention that the provided time is the 
>>> time at which the request failed not when it was sent to your servers (that 
>>> time is ~30-40 seconds before).
>>>
>>> Concerning the thread-safety recommendations I'm sure that the 
>>> ReportDownloader and its Session are not used in multiple threads in our 
>>> code.
>>>
>>> Further information: 
>>> Checking our errors I found an interesting pattern, failing requests 
>>> always take at least 30 seconds (usually 30-31) while successful ones are 
>>> most likely to be around 1 second.
>>>
>>> Maybe a stupid thought but could it be a something like the java-library 
>>> timing out after 30 seconds and retrying using the provided 
>>> session/ReportDownloader again which then violates the threadSafety and 
>>> results in invalid requests?
>>>
>>> Best Regards,
>>> Ron
>>>
>>>
>>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
>>> API Team):

 Hi Ronald,

 I searched the logs on our side and could not find either of those 
 requests. Are you sure that they were submitted for the account ID you 
 mentioned?

 By the way, did you check if you're adhering to the thread safety 
 guidelines I mentioned earlier? I just want to make sure we can rule that 
 out as a possible cause of the errors.

 Thanks,
 Josh, AdWords API Team

 On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> thx for the hints.
> Concerning the requested information I can give you 2 identical 
> request where one succeeded and the other one failed with a 400 as shown 
> in 
> my last message.
>
> failed:
> time: 27.03.18 01:06:08 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> succeeded:
> time: 27.03.18 03:06:30 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> Best Regards, Ron
>
> Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff 
> (AdWords API Team):
>>
>> Hi Raneen,
>>
>> From our logs, it appears that your requests are most frequently 
>> failing with the following errors:
>>
>>- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
>>- AuthorizationError.USER_PERMISSION_DENIED
>>- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
>>
>> Could you share a report request that failed, with any sensitive 
>> information removed (developer token, OAuth access token, etc.)?
>>
>> Also, I see that you are using the client library for Java. Are you 
>> adhering to the thread-safety recommendations 
>> 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Dorian Kind]

Hi all,

I thought I posted previously in this thread, but it looks like my message 
has been deleted. I just wanted to chime in that we've also been seeing 
these sporadic report failures that return a HTTP 400 status code and no 
reponse content. They don't seem to be reproducible, from what we can tell 
and are most likely not the result of an expired OAuth token or a malformed 
report definition as both of these cases give detailed error messages.
We don't feel comfortable automatically retrying report download requests 
for error codes below 500, so it'd be great if the Adwords team could shed 
some light on the issue.

Thanks and best regards,
Dorian

On Friday, 30 March 2018 15:15:38 UTC+2, Josh Radcliff (AdWords API Team) 
wrote:
>
> Hi Ron,
>
> Sorry, I'm still having trouble locating those requests in our logs. Would 
> you mind sending over the customer ID where your developer token is 
> registered? You can send it only to me by clicking *Reply privately to 
> author*.
>
> Regarding the timeout theory, the ReportDownloader won't automatically 
> retry requests. However, if you think timeouts are the root cause here, you 
> can adjust the timeout for report downloads programmatically or in your 
> *ads.properties* file. Check out this section of the ads.properties file 
> 
>  for 
> details.
>
> Thanks,
> Josh, AdWords API Team
>
> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>
>> Hi Josh,
>>
>> I checked the request data that I provided you and they are exactly what 
>> I can see in my logs. Maybe I should mention that the provided time is the 
>> time at which the request failed not when it was sent to your servers (that 
>> time is ~30-40 seconds before).
>>
>> Concerning the thread-safety recommendations I'm sure that the 
>> ReportDownloader and its Session are not used in multiple threads in our 
>> code.
>>
>> Further information: 
>> Checking our errors I found an interesting pattern, failing requests 
>> always take at least 30 seconds (usually 30-31) while successful ones are 
>> most likely to be around 1 second.
>>
>> Maybe a stupid thought but could it be a something like the java-library 
>> timing out after 30 seconds and retrying using the provided 
>> session/ReportDownloader again which then violates the threadSafety and 
>> results in invalid requests?
>>
>> Best Regards,
>> Ron
>>
>>
>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Hi Ronald,
>>>
>>> I searched the logs on our side and could not find either of those 
>>> requests. Are you sure that they were submitted for the account ID you 
>>> mentioned?
>>>
>>> By the way, did you check if you're adhering to the thread safety 
>>> guidelines I mentioned earlier? I just want to make sure we can rule that 
>>> out as a possible cause of the errors.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:

 Hi Josh,

 thx for the hints.
 Concerning the requested information I can give you 2 identical request 
 where one succeeded and the other one failed with a 400 as shown in my 
 last 
 message.

 failed:
 time: 27.03.18 01:06:08 CEST
 googleAdwordsAccountId: 685-366-2732
 SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
 WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;

 succeeded:
 time: 27.03.18 03:06:30 CEST
 googleAdwordsAccountId: 685-366-2732
 SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
 WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;

 Best Regards, Ron

 Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff 
 (AdWords API Team):
>
> Hi Raneen,
>
> From our logs, it appears that your requests are most frequently 
> failing with the following errors:
>
>- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
>- AuthorizationError.USER_PERMISSION_DENIED
>- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
>
> Could you share a report request that failed, with any sensitive 
> information removed (developer token, OAuth access token, etc.)?
>
> Also, I see that you are using the client library for Java. Are you 
> adhering to the thread-safety recommendations 
> ? 
> For example, you should not use a *ReportDownloader* instance within 
> multiple threads. Doing so will produce unpredictable behavior, such as 
> malformed requests or issues parsing responses.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
> (AdWords API Team) wrote:

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ron,

Sorry, I'm still having trouble locating those requests in our logs. Would 
you mind sending over the customer ID where your developer token is 
registered? You can send it only to me by clicking *Reply privately to 
author*.

Regarding the timeout theory, the ReportDownloader won't automatically 
retry requests. However, if you think timeouts are the root cause here, you 
can adjust the timeout for report downloads programmatically or in your 
*ads.properties* file. Check out this section of the ads.properties file 

 for 
details.

Thanks,
Josh, AdWords API Team

On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> I checked the request data that I provided you and they are exactly what I 
> can see in my logs. Maybe I should mention that the provided time is the 
> time at which the request failed not when it was sent to your servers (that 
> time is ~30-40 seconds before).
>
> Concerning the thread-safety recommendations I'm sure that the 
> ReportDownloader and its Session are not used in multiple threads in our 
> code.
>
> Further information: 
> Checking our errors I found an interesting pattern, failing requests 
> always take at least 30 seconds (usually 30-31) while successful ones are 
> most likely to be around 1 second.
>
> Maybe a stupid thought but could it be a something like the java-library 
> timing out after 30 seconds and retrying using the provided 
> session/ReportDownloader again which then violates the threadSafety and 
> results in invalid requests?
>
> Best Regards,
> Ron
>
>
> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
> API Team):
>>
>> Hi Ronald,
>>
>> I searched the logs on our side and could not find either of those 
>> requests. Are you sure that they were submitted for the account ID you 
>> mentioned?
>>
>> By the way, did you check if you're adhering to the thread safety 
>> guidelines I mentioned earlier? I just want to make sure we can rule that 
>> out as a possible cause of the errors.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>>>
>>> Hi Josh,
>>>
>>> thx for the hints.
>>> Concerning the requested information I can give you 2 identical request 
>>> where one succeeded and the other one failed with a 400 as shown in my last 
>>> message.
>>>
>>> failed:
>>> time: 27.03.18 01:06:08 CEST
>>> googleAdwordsAccountId: 685-366-2732
>>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
>>> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>>>
>>> succeeded:
>>> time: 27.03.18 03:06:30 CEST
>>> googleAdwordsAccountId: 685-366-2732
>>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
>>> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>>>
>>> Best Regards, Ron
>>>
>>> Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff (AdWords 
>>> API Team):

 Hi Raneen,

 From our logs, it appears that your requests are most frequently 
 failing with the following errors:

- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
- AuthorizationError.USER_PERMISSION_DENIED
- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT

 Could you share a report request that failed, with any sensitive 
 information removed (developer token, OAuth access token, etc.)?

 Also, I see that you are using the client library for Java. Are you 
 adhering to the thread-safety recommendations 
 ? 
 For example, you should not use a *ReportDownloader* instance within 
 multiple threads. Doing so will produce unpredictable behavior, such as 
 malformed requests or issues parsing responses.

 Thanks,
 Josh, AdWords API Team

 On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
 (AdWords API Team) wrote:
>
> Hi Ron, 
>
> The V201702 version of the API is deprecated and all calls made to 
> this version of the API will return an error. v201802 
> 
>  is 
> the most recent version of the API currently available. We strongly 
> recommend that you migrate to this version. For future reference, please 
> find the deprecation schedule 
>  for 
> various API versions. The resources given below might be helpful for you 
> in 
> migration: 
>
>- v201802 migration guide 
>
> 
>- v201710 migration guide 
>
> 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Ronald Findling]

Hi Josh,

I checked the request data that I provided you and they are exactly what I 
can see in my logs. Maybe I should mention that the provided time is the 
time at which the request failed not when it was sent to your servers (that 
time is ~30-40 seconds before).

Concerning the thread-safety recommendations I'm sure that the 
ReportDownloader and its Session are not used in multiple threads in our 
code.

Further information: 
Checking our errors I found an interesting pattern, failing requests always 
take at least 30 seconds (usually 30-31) while successful ones are most 
likely to be around 1 second.

Maybe a stupid thought but could it be a something like the java-library 
timing out after 30 seconds and retrying using the provided 
session/ReportDownloader again which then violates the threadSafety and 
results in invalid requests?

Best Regards,
Ron


Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
API Team):
>
> Hi Ronald,
>
> I searched the logs on our side and could not find either of those 
> requests. Are you sure that they were submitted for the account ID you 
> mentioned?
>
> By the way, did you check if you're adhering to the thread safety 
> guidelines I mentioned earlier? I just want to make sure we can rule that 
> out as a possible cause of the errors.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>>
>> Hi Josh,
>>
>> thx for the hints.
>> Concerning the requested information I can give you 2 identical request 
>> where one succeeded and the other one failed with a 400 as shown in my last 
>> message.
>>
>> failed:
>> time: 27.03.18 01:06:08 CEST
>> googleAdwordsAccountId: 685-366-2732
>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT WHERE 
>> CountryCriteriaId = 2826 DURING 20180225,20180327;
>>
>> succeeded:
>> time: 27.03.18 03:06:30 CEST
>> googleAdwordsAccountId: 685-366-2732
>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT WHERE 
>> CountryCriteriaId = 2826 DURING 20180225,20180327;
>>
>> Best Regards, Ron
>>
>> Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Hi Raneen,
>>>
>>> From our logs, it appears that your requests are most frequently failing 
>>> with the following errors:
>>>
>>>- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
>>>- AuthorizationError.USER_PERMISSION_DENIED
>>>- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
>>>
>>> Could you share a report request that failed, with any sensitive 
>>> information removed (developer token, OAuth access token, etc.)?
>>>
>>> Also, I see that you are using the client library for Java. Are you 
>>> adhering to the thread-safety recommendations 
>>> ? 
>>> For example, you should not use a *ReportDownloader* instance within 
>>> multiple threads. Doing so will produce unpredictable behavior, such as 
>>> malformed requests or issues parsing responses.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
>>> (AdWords API Team) wrote:

 Hi Ron, 

 The V201702 version of the API is deprecated and all calls made to this 
 version of the API will return an error. v201802 
 
  is 
 the most recent version of the API currently available. We strongly 
 recommend that you migrate to this version. For future reference, please 
 find the deprecation schedule 
  for 
 various API versions. The resources given below might be helpful for you 
 in 
 migration: 

- v201802 migration guide 

 
- v201710 migration guide 

 
- v201708 migration guide 

  
 (useful 
if you are migrating from v201705)
- Release notes 


 You could follow our Google Ads Developer blog 
  or 
 the AdWords API Announcements forum 
  to 
 make sure that you are not missing any announcements about the API in the 
 future. Please let me know if you have any further questions. 

 Thanks,
 Sreelakshmi, AdWords API Team

>>>

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

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ronald,

I searched the logs on our side and could not find either of those 
requests. Are you sure that they were submitted for the account ID you 
mentioned?

By the way, did you check if you're adhering to the thread safety 
guidelines I mentioned earlier? I just want to make sure we can rule that 
out as a possible cause of the errors.

Thanks,
Josh, AdWords API Team

On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> thx for the hints.
> Concerning the requested information I can give you 2 identical request 
> where one succeeded and the other one failed with a 400 as shown in my last 
> message.
>
> failed:
> time: 27.03.18 01:06:08 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT WHERE 
> CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> succeeded:
> time: 27.03.18 03:06:30 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT WHERE 
> CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> Best Regards, Ron
>
> Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff (AdWords 
> API Team):
>>
>> Hi Raneen,
>>
>> From our logs, it appears that your requests are most frequently failing 
>> with the following errors:
>>
>>- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
>>- AuthorizationError.USER_PERMISSION_DENIED
>>- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
>>
>> Could you share a report request that failed, with any sensitive 
>> information removed (developer token, OAuth access token, etc.)?
>>
>> Also, I see that you are using the client library for Java. Are you 
>> adhering to the thread-safety recommendations 
>> ? 
>> For example, you should not use a *ReportDownloader* instance within 
>> multiple threads. Doing so will produce unpredictable behavior, such as 
>> malformed requests or issues parsing responses.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
>> (AdWords API Team) wrote:
>>>
>>> Hi Ron, 
>>>
>>> The V201702 version of the API is deprecated and all calls made to this 
>>> version of the API will return an error. v201802 
>>> 
>>>  is 
>>> the most recent version of the API currently available. We strongly 
>>> recommend that you migrate to this version. For future reference, please 
>>> find the deprecation schedule 
>>>  for 
>>> various API versions. The resources given below might be helpful for you in 
>>> migration: 
>>>
>>>- v201802 migration guide 
>>>
>>>- v201710 migration guide 
>>>
>>>- v201708 migration guide 
>>>
>>>  
>>> (useful 
>>>if you are migrating from v201705)
>>>- Release notes 
>>>
>>>
>>> You could follow our Google Ads Developer blog 
>>>  or 
>>> the AdWords API Announcements forum 
>>>  to 
>>> make sure that you are not missing any announcements about the API in the 
>>> future. Please let me know if you have any further questions. 
>>>
>>> Thanks,
>>> Sreelakshmi, 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/b744e7f7-addf-4147-a185-6688e9ea9a12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Ronald Findling]

Hi Josh,

thx for the hints.
Concerning the requested information I can give you 2 identical request 
where one succeeded and the other one failed with a 400 as shown in my last 
message.

failed:
time: 27.03.18 01:06:08 CEST
googleAdwordsAccountId: 685-366-2732
SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT WHERE 
CountryCriteriaId = 2826 DURING 20180225,20180327;

succeeded:
time: 27.03.18 03:06:30 CEST
googleAdwordsAccountId: 685-366-2732
SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT WHERE 
CountryCriteriaId = 2826 DURING 20180225,20180327;

Best Regards, Ron

Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff (AdWords 
API Team):
>
> Hi Raneen,
>
> From our logs, it appears that your requests are most frequently failing 
> with the following errors:
>
>- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
>- AuthorizationError.USER_PERMISSION_DENIED
>- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
>
> Could you share a report request that failed, with any sensitive 
> information removed (developer token, OAuth access token, etc.)?
>
> Also, I see that you are using the client library for Java. Are you 
> adhering to the thread-safety recommendations 
> ? For 
> example, you should not use a *ReportDownloader* instance within multiple 
> threads. Doing so will produce unpredictable behavior, such as malformed 
> requests or issues parsing responses.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
> (AdWords API Team) wrote:
>>
>> Hi Ron, 
>>
>> The V201702 version of the API is deprecated and all calls made to this 
>> version of the API will return an error. v201802 
>> 
>>  is 
>> the most recent version of the API currently available. We strongly 
>> recommend that you migrate to this version. For future reference, please 
>> find the deprecation schedule 
>>  for 
>> various API versions. The resources given below might be helpful for you in 
>> migration: 
>>
>>- v201802 migration guide 
>>
>>- v201710 migration guide 
>>
>>- v201708 migration guide 
>> 
>> (useful 
>>if you are migrating from v201705)
>>- Release notes 
>>
>>
>> You could follow our Google Ads Developer blog 
>>  or 
>> the AdWords API Announcements forum 
>>  to 
>> make sure that you are not missing any announcements about the API in the 
>> future. Please let me know if you have any further questions. 
>>
>> Thanks,
>> Sreelakshmi, 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/b8a826ea-3761-4916-81c1-dc330bcef254%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ron, Raneen,

In my previous post, I mistakenly said that the list of errors I provided 
was for Raneen, but I just realized that they were actually for you, Ron. 
Sorry about that!

*Ron*, could you check out my previous post and the questions/items I 
highlighted there?

Thanks,
Josh, AdWords API Team

On Wednesday, March 21, 2018 at 6:18:17 AM UTC-4, Ronald Findling wrote:
>
> Hi Sreelakshmi,
> sorry, I somehow mixed up versions here -- we are actually using `
> com.google.api.ads.adwords.axis.v201710`
>
>
> Am Dienstag, 20. März 2018 20:06:14 UTC+1 schrieb Sreelakshmi Sasidharan 
> (AdWords API Team):
>>
>> Hi Ron, 
>>
>> The V201702 version of the API is deprecated and all calls made to this 
>> version of the API will return an error. v201802 
>> 
>>  is 
>> the most recent version of the API currently available. We strongly 
>> recommend that you migrate to this version. For future reference, please 
>> find the deprecation schedule 
>>  for 
>> various API versions. The resources given below might be helpful for you in 
>> migration: 
>>
>>- v201802 migration guide 
>>
>>- v201710 migration guide 
>>
>>- v201708 migration guide 
>> 
>> (useful 
>>if you are migrating from v201705)
>>- Release notes 
>>
>>
>> You could follow our Google Ads Developer blog 
>>  or 
>> the AdWords API Announcements forum 
>>  to 
>> make sure that you are not missing any announcements about the API in the 
>> future. Please let me know if you have any further questions. 
>>
>> Thanks,
>> Sreelakshmi, 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/c7249dd2-b47b-49fb-8af9-61d99595ee89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Ronald Findling]

Hi Sreelakshmi,
sorry, I somehow mixed up versions here -- we are actually using `
com.google.api.ads.adwords.axis.v201710`


Am Dienstag, 20. März 2018 20:06:14 UTC+1 schrieb Sreelakshmi Sasidharan 
(AdWords API Team):
>
> Hi Ron, 
>
> The V201702 version of the API is deprecated and all calls made to this 
> version of the API will return an error. v201802 
> 
>  is 
> the most recent version of the API currently available. We strongly 
> recommend that you migrate to this version. For future reference, please 
> find the deprecation schedule 
>  for various 
> API versions. The resources given below might be helpful for you in 
> migration: 
>
>- v201802 migration guide 
>
>- v201710 migration guide 
>
>- v201708 migration guide 
> 
> (useful 
>if you are migrating from v201705)
>- Release notes 
>
>
> You could follow our Google Ads Developer blog 
>  or the 
> AdWords 
> API Announcements forum 
>  to 
> make sure that you are not missing any announcements about the API in the 
> future. Please let me know if you have any further questions. 
>
> Thanks,
> Sreelakshmi, 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/b8d425f6-a4de-444c-9c5a-2ef4a8d72299%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Raneen,

>From our logs, it appears that your requests are most frequently failing 
with the following errors:

   - ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
   - AuthorizationError.USER_PERMISSION_DENIED
   - ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
   
Could you share a report request that failed, with any sensitive 
information removed (developer token, OAuth access token, etc.)?

Also, I see that you are using the client library for Java. Are you 
adhering to the thread-safety recommendations 
? For 
example, you should not use a *ReportDownloader* instance within multiple 
threads. Doing so will produce unpredictable behavior, such as malformed 
requests or issues parsing responses.

Thanks,
Josh, AdWords API Team

On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
(AdWords API Team) wrote:
>
> Hi Ron, 
>
> The V201702 version of the API is deprecated and all calls made to this 
> version of the API will return an error. v201802 
> 
>  is 
> the most recent version of the API currently available. We strongly 
> recommend that you migrate to this version. For future reference, please 
> find the deprecation schedule 
>  for various 
> API versions. The resources given below might be helpful for you in 
> migration: 
>
>- v201802 migration guide 
>
>- v201710 migration guide 
>
>- v201708 migration guide 
> 
> (useful 
>if you are migrating from v201705)
>- Release notes 
>
>
> You could follow our Google Ads Developer blog 
>  or the 
> AdWords 
> API Announcements forum 
>  to 
> make sure that you are not missing any announcements about the API in the 
> future. Please let me know if you have any further questions. 
>
> Thanks,
> Sreelakshmi, 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/5a8332ee-7ba4-4ad1-9664-236e3bfaff35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Dorian Kind]

Hi,

FWIW, we've also noticed these intermittent 400 Bad Request errors when 
downloading reports. We have not seen these specific failures before.
>From what I can tell in our case, they do not seem to be related to OAuth2 
access token issues as those fail with a message of 
"AuthenticationError.OAUTH_TOKEN_INVALID", while the observed errors do not 
seem to have a response body. I don't think that the report definition is 
faulty, either, as the requests are correctly processed when we retry them.

Best regards,
Dorian

On Tuesday, 20 March 2018 09:10:42 UTC+1, Ronald Findling wrote:
>
> 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/09147701-c63c-4628-8768-f991e8ff3b22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Sreelakshmi Sasidharan (AdWords API Team)' via AdWords API Forum]

Hi Ron, 

The V201702 version of the API is deprecated and all calls made to this 
version of the API will return an error. v201802 

 is 
the most recent version of the API currently available. We strongly 
recommend that you migrate to this version. For future reference, please 
find the deprecation schedule 
 for various 
API versions. The resources given below might be helpful for you in 
migration: 

   - v201802 migration guide 
   
   - v201710 migration guide 
   
   - v201708 migration guide 
    
(useful 
   if you are migrating from v201705)
   - Release notes 
   

You could follow our Google Ads Developer blog 
 or the 
AdWords 
API Announcements forum 
 to make 
sure that you are not missing any announcements about the API in the 
future. Please let me know if you have any further questions. 

Thanks,
Sreelakshmi, 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/81113600-2ae9-40dd-a9bb-4fe32fcb58ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Ronald Findling]

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.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[avathanakamsang]

Hello AdWords API Team,

I am experiencing the same issue. Can you let me know who I should reach 
out inorder to send you the logs?

Thanks,
Andrew

On Wednesday, January 10, 2018 at 12:03:48 PM UTC-8, Anash P. Oommen 
(AdWords API Team) wrote:
>
> Hi Raneen,
>
> 400 exception happens if there's something wrong with the request being 
> sent to the server. It could be because of an expired session; it could be 
> because of a malformed request. Capturing the logs is the best way to tell 
> for sure, because that gives you the raw HTTP response that the client 
> library can't somehow seem to parse.
>
> Cheers
> Anash P. Oommen
> AdWords API Advisor.
>
> On Wednesday, January 10, 2018 at 5:25:23 AM UTC-5, raneenb...@gmail.com 
>  wrote:
>>
>> 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/f0107f6a-a84c-4b99-bcaa-4af52220cfe1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Anash P. Oommen (AdWords API Team)' via AdWords API Forum]

Hi Raneen,

400 exception happens if there's something wrong with the request being 
sent to the server. It could be because of an expired session; it could be 
because of a malformed request. Capturing the logs is the best way to tell 
for sure, because that gives you the raw HTTP response that the client 
library can't somehow seem to parse.

Cheers
Anash P. Oommen
AdWords API Advisor.

On Wednesday, January 10, 2018 at 5:25:23 AM UTC-5, 
raneenbsais...@gmail.com wrote:
>
> 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/6740605b-ed67-4ec8-8689-6d132327e55d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[raneenbsais212]

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/49a02565-1995-4bf3-bbd8-34978870fc1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Anash P. Oommen (AdWords API Team)' via AdWords API Forum]

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/ea0ff3b3-1ebe-44db-a9db-cab9c1a375db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Raneen Bsais' via AdWords API Forum]

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/221e663f-78e7-4656-86db-00f9c190c450%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Peter Oliquino' via AdWords API Forum]

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/857ca448-b738-4f0b-9577-37d59f75f59c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[raneen.bsais via AdWords API Forum]

*clientCustomerId  *5140862830
*startDate*  2017-12-27
*endDate  2018-01-02*

thanks
raneen

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/82b31048-7e12-41b2-a1e6-92a9a6292481%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Peter Oliquino' via AdWords API Forum]

Hi,

In order to better investigate your concern, could you provide your 
*clientCustomerId*, the values of your *startDate* and *endDate*, and 
respond to me privately via the *Reply privately to author* option?

Thanks and 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/33f9d680-09a8-4b6e-906d-515762748cfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.