Hello, I'm sorry that you're running into this. Our core engineering team has noticed a recent spate of 502 errors in our Production services, and are taking steps to isolate and resolve the problem.
502 "Bad Gateway" errors are most common in our environment when one of our backend servers has trouble communicating with another internal server, and is normally not something that you as an end user can do to avoid. There shouldn't be any connection to whether you're running your code in the debugger or not, though if you code hits a different set of backend servers in between calls you may or may not see the errors. I'll update the thread with more information when I have it. Cheers, -Jeff Posnick, AdWords API Team On Apr 1, 2:39 pm, WebVisible <[email protected]> wrote: > We have an application that talks to the AdWords API. It's written > in .NET 3.5 C# and talking to v13 of the AdWords API. The application > works just fine in production, but when trying to debug some calls, it > returns a 502 "Bad Gateway" error repeatedly. Specifically, we try to > call scheduleReportJob() and it fails. Retrying over and over doesn't > work. Any idea why it's specific to debugging and not production? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
