Thank you Nadine! As a follow-up, the problem did not occur after March 1. I'll add 404 as a reason to attempt a retry on the report - probably after a time-out of 30 seconds (and 60-120 seconds on next retries). But do let me know when you learn the reason.
Cheers, Zweitze. On Friday, March 3, 2017 at 12:12:47 AM UTC+1, Nadine Sundquist (AdWords API Team) wrote: > > Greetings Zweitze! > > It's always nice to hear from a friendly virtual voice! I hope you are > doing well. Now, let's dive into your issue here. I haven't heard of any > issues with pulling reports recently, but I have seen 404 errors from the > API before when a server is having difficulty serving. It's not very > common, but I don't want to discount it as a possibility. The best thing > you can do is retry. We're taking a look to see if one of our servers is > having difficulty or if it could be something else causing it. I'll get > back to you soon. If you don't hear from me soon, feel free to bump this > thread. > > Cheers, > Nadine, AdWords API Team > > On Thursday, March 2, 2017 at 8:36:19 AM UTC-5, Zweitze wrote: >> >> Hi, >> >> Can someone look into this? Every day we request thousands of reports >> with the API, for many years now. This morning we got HTTP 404 twice. >> The version is v201607. >> We do not have the requests, but we do log the response headers, maybe >> this is some help to you: >> >> First error occurred at about 04:12 CEST while requesting >> ADGROUP_PERFORMANCE_REPORT for 105-084-2731. >> We received 12 Response headers: >> >> *Name* >> *Value* >> Pragma >> no-cache >> Content-Encoding >> >> X-Content-Type-Options >> nosniff >> X-Frame-Options >> SAMEORIGIN >> X-XSS-Protection >> 1; mode=block >> Alt-Svc >> quic=":443"; ma=2592000; v="36,35,34" >> Transfer-Encoding >> chunked >> Cache-Control >> no-cache, no-store, max-age=0, must-revalidate >> Content-Type >> text/html; charset=UTF-8 >> Date >> Thu, 02 Mar 2017 03:12:10 GMT >> Expires >> Mon, 01 Jan 1990 00:00:00 GMT >> Server >> GSE >> >> Second error occurred at about 04:16 CEST while requesting >> CAMPAIGN_NEGATIVE_PLACEMENTS_PERFORMANCE_REPORT for 984-674-9135 >> We received 12 Response headers: >> >> *Name* >> *Value* >> Pragma >> no-cache >> Content-Encoding >> >> X-Content-Type-Options >> nosniff >> X-Frame-Options >> SAMEORIGIN >> X-XSS-Protection >> 1; mode=block >> Alt-Svc >> quic=":443"; ma=2592000; v="36,35,34" >> Transfer-Encoding >> chunked >> Cache-Control >> no-cache, no-store, max-age=0, must-revalidate >> Content-Type >> text/html; charset=UTF-8 >> Date >> Thu, 02 Mar 2017 03:16:22 GMT >> Expires >> Mon, 01 Jan 1990 00:00:00 GMT >> Server >> GSE >> >> Any idea? Is HTTP 404 a valid response now, if so, how should we handle >> that situation? >> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/94c9fd54-934a-403a-bd27-0b98cd6521e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
