So yes, this does appear to be working again. As for what changed... my understanding is that a scheduled, gradual restart of the AdWords API servers took place, and upon coming back online the issue resolved itself. Given that, I'd be hard-pressed to say that it's permanently fixed, and we're leaving the bug open for further investigation.
As for whether it's ready for use: I obviously can't guarantee that the issue will never crop up again. I'd think that it's as ready as it's going to be for a while, though. As long as you code around the possibility that -1 might be returned (which is good practice anyway) I don't see any reason to wait. Cheers, -Jeff Posnick, AdWords API Team On Dec 10, 4:38 am, Aleksandar Bradaric <[EMAIL PROTECTED]> wrote: > Hi, > > > And, just so you know, this continues to be investigated. If it makes > > anyone feel better, it's proving to be a rather mysterious issue (as > > opposed to some more mundane bug). > > I think I can see some real volume numbers now :) Does this mean that > you've found the bug? Is it fixed and ready to use, or should we wait > for the green light? > > Thanks. > > Take care, > Aleksandar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
