AdWords API users out there, you may have noticed that Google is returning errors for some of your operations and calls. Reports came in on April 1st at a Google Groups thread, which has been confirmed by Google.
Googler, Jeff Posnick from the AdWords API Team said:
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.
There have not been many complaints. That can be because of three possible reasons:
- This is not a major issue and is only impacting a few people.
- Few people use this feature
- People have not yet looked at their automated reports to see these errors yet.
Forum discussion at Google Groups.