Hello Bartek, I actually was just going to post to say that the word from the engineering team is that this should have been fixed in a change on the backend that went live over the weekend. But I'm assuming you tested today when you say that it's still not working, so the change that was made may have been ineffective.
It would be helpful if you could make the API call one more time with logging enabled and pass along the most recent requestId SOAP response header so that I could present that to the engineering team have them look into whether the attempt to update your campaign is currently failing for the same reason or if there is something else at play. Thanks! Cheers, -Jeff Posnick, AdWords API Team On Sep 1, 5:02 am, Bartek Jakubski <[EMAIL PROTECTED]> wrote: > On Aug 27, 9:10 pm, AdWords API Advisor <[EMAIL PROTECTED]> > wrote: > > > Hello Bartek, > > > Okay, if it failed via the web interface too then there's definitely > > something corrupt with how that campaign is represented in systems. > > I'll flag down someone who knows about the AdWords backend to see what > > they can do to resolve the issue. > > Are there any news here? We are unfortunately still getting those > errors in this account... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
