This topic was somehow below my radar, but I occasionally get this too. See 
here <https://groups.google.com/d/msg/adwords-api/zgGyRXYUF4k/eW8ub-asCAAJ> 
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 
>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/ads.properties#L47>
>>  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 
>>>>>> <https://github.com/googleads/googleads-java-lib/wiki/Thread-Safety>? 
>>>>>> 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 
>>>>>>> <https://googleadsdeveloper.blogspot.com/2018/02/announcing-v201802-of-adwords-api.html>
>>>>>>>  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 
>>>>>>> <https://developers.google.com/adwords/api/docs/sunset-dates> for 
>>>>>>> various API versions. The resources given below might be helpful for 
>>>>>>> you in 
>>>>>>> migration: 
>>>>>>>
>>>>>>>    - v201802 migration guide 
>>>>>>>    
>>>>>>> <https://developers.google.com/adwords/api/docs/guides/migration/v201802>
>>>>>>>    - v201710 migration guide 
>>>>>>>    
>>>>>>> <https://developers.google.com/adwords/api/docs/guides/migration/v201710>
>>>>>>>    - v201708 migration guide 
>>>>>>>    
>>>>>>> <https://developers.google.com/adwords/api/docs/guides/migration/v201708>
>>>>>>>  (useful 
>>>>>>>    if you are migrating from v201705)
>>>>>>>    - Release notes 
>>>>>>>    <https://developers.google.com/adwords/api/docs/reference/>
>>>>>>>
>>>>>>> You could follow our Google Ads Developer blog 
>>>>>>> <https://googleadsdeveloper.blogspot.com/search/label/adwords_api> or 
>>>>>>> the AdWords API Announcements forum 
>>>>>>> <https://groups.google.com/forum/#!forum/adwordsapi-announcements> 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/9e351ae1-2df6-4606-9afe-ab171f1c66b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
      • ... Andrew Vathanakamsang
  • ... Ronald Findling
    • ... 'Sreelakshmi Sasidharan (AdWords API Team)' via AdWords API Forum
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • ... Ronald Findling
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • ... Ronald Findling
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • ... Dorian Kind
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • ... Zweitze
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • ... Ronald Findling
      • ... Ronald Findling
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • ... Ronald Findling
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • ... Dorian Kind
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum
      • ... Ronald Findling

Reply via email to