Hi Josh, is there any update on this issue? The situation is still the same and we haven't noticed an improvement over the past days (it also did not get worse, though).
Thanks, Stefan Am Freitag, 9. September 2016 19:49:14 UTC+2 schrieb Josh Radcliff (AdWords API Team): > > Hi Stefan, > > Thanks for sending over that info. I looked at those requests and didn't > see any errors in terms of AdWords API handling, which suggests this may be > an issue at a different layer on our side. I'll keep digging and let you > know what I find. > > Cheers, > Josh, AdWords API Team > > On Friday, September 9, 2016 at 10:31:58 AM UTC-4, Stefan Kleine Stegemann > wrote: >> >> >> Hi Josh, >> >> I sent you a private mail with some information. >> >> I hope that helps. >> >> Thanks, >> Stefan >> >> >> Am Freitag, 9. September 2016 15:58:01 UTC+2 schrieb Josh Radcliff >> (AdWords API Team): >>> >>> Hi Stefan, >>> >>> Thanks for looking. Since you aren't getting a response back due to the >>> timeout, you won't have a *requestId* (which is part of the response >>> payload). However, if you have a specific ad group ID or campaign ID where >>> you've encountered timeouts, along with the timestamp (including timezone) >>> of the timed out request, I may be able to find what went wrong with that >>> particular request. >>> >>> Thanks, >>> Josh, AdWords API Team >>> >>> On Friday, September 9, 2016 at 7:27:56 AM UTC-4, Stefan Kleine >>> Stegemann wrote: >>>> >>>> >>>> Hi Josh, >>>> >>>> i'm sorry but I wasn't able to find a request with a request-id in our >>>> logs. I inspected the soap dumps from failed requests and found none with >>>> a >>>> request id. I found some other failed requests where the id was displayed >>>> but these requests failed because of "normal" errors (such as user >>>> permission denied). I wonder what's the rule for request having an id or >>>> not? >>>> >>>> Cheers, >>>> Stefan >>>> >>>> Am Donnerstag, 8. September 2016 23:41:27 UTC+2 schrieb Josh Radcliff >>>> (AdWords API Team): >>>>> >>>>> Hi, >>>>> >>>>> Would either of you happen to have a particularly unique example >>>>> request where this failed? It looks like you're not getting back a >>>>> *requestId* in this case, but if your request contained a string or >>>>> ID that was unique to that request, that would help me track down what >>>>> happened. >>>>> >>>>> If you would prefer, you can send the information only to me by >>>>> clicking *Reply privately to author* on this message. >>>>> >>>>> Thanks, >>>>> Josh, 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. 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/b4855d56-3aa5-4bb3-b844-1a2e5b0c59b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
