Hello Tim, So yesterday's occurrence is actually something that the core engineering team knows the root cause of. There was a loss of connectivity between one particular set of AdWords API servers and the backend data store that contains reports data yesterday morning for several hours. There is retry/failover logic in place that should have protected most users from seeing anything other than slightly increased response times, but they did see a handful of outright failures to fetch report data due to this.
But... it's not a type of failure that has occurred previously, so the engineering team isn't convinced that it has particular insight to offer into the root cause of the previous occurrences. \ Cheers, -Jeff Posnick, AdWords API Team On Nov 24, 6:32 pm, tozor <[EMAIL PROTECTED]> wrote: > We had a reoccurence of this error at 7:30AM PST. > > Thanks. > > Tim Ozor > > On Oct 14, 12:30 pm, AdWords API Advisor > > <[EMAIL PROTECTED]> wrote: > > I wanted to update folks after speaking to the engineering team about > > this again. > > > There's speculation that these bad URLs might be returned during a > > period of time in which the backend datastore is in a particular state > > (apologies for not being able to get more specific than that). They're > > matching up the timestamps from the sample failures everyone has > > already provided, but what they'd really like is to be notified the > > next time this happens so that they could try to catch things live. > > > So, please don't hesitate to post again about this behavior soon after > > you see it. I'll bring it to the engineers' immediate attention when > > you do. > > > Cheers, > > -Jeff Posnick, AdWords API Team > > > On Oct 2, 1:19 pm, tozor <[EMAIL PROTECTED]> wrote: > > > > I saw it several times on Friday during the day, but have not seen it > > > since then. > > > > Tim Ozor > > > > On Oct 2, 10:07 am, AdWords API Advisor <[EMAIL PROTECTED]> > > > wrote: > > > > > Hello, > > > > > The bug is in with the engineering team, but there's no update on it > > > > yet. How frequently are folks experiencing this behavior over the past > > > > day or so? If this was taking place primarily last week that's a good > > > > data point to pass back to the engineers. > > > > > Cheers, > > > > -Jeff Posnick, AdWords API Team > > > > > On Sep 29, 4:35 am, Albert <[EMAIL PROTECTED]> wrote: > > > > > > Please let us know when this is resolved. In the mean time we've > > > > > implemented a re-try ordering a new report if the download url throws > > > > > 404 not found. The problem with this is we are paying quota for each > > > > > new report although the problem is not on our side. > > > > > > regards, > > > > > Albert --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
