High rates of connection failures and report errors

19 views
Skip to first unread message

Nick

unread,
Jan 16, 2020, 3:54:44 PM1/16/20
to AdWords API and Google Ads API Forum
Good morning,

We have some custom reporting software that collects spend details on dozens of our client accounts and reviews the campaigns.

We're running into a lot of connection issues while this tries to run, it started to run a couple of hours ago, but not sure on the state of things before then.

We can get details for a couple, then see "Failed to connect to www.googleapis.com port 443: Connection timed out" for the next one.
Or it might work fine for that one, but then get "Connection failed; https://adwords.google.com/api/adwords/reportdownload/v201809 Connection timed out"

It's inconsistent, what worked 10 minutes ago will now fail or vice versa.

Any network issues we should know about? This has run fine for more than a few years, no changes on our end last few months.

Coming from NZ.

Thanks
Nick

Google Ads API Forum Advisor Prod

unread,
Jan 17, 2020, 2:33:50 PM1/17/20
to wizar...@gmail.com, adwor...@googlegroups.com

Hello Nick,

Thank you for reaching out. Could you please share the complete request and response logs along with the client customer ids against which you are observing these errors for me to take a look into this further and assist you better? Also, if you are encountering timeouts when generating reports, it could mean that you maybe downloading a huge amount of data all at once. To avoid these timeouts, could you please try to break down your reports by adding filters or by narrowing down the date range as specified in the shared guide? 

P.S. Please use Reply privately to author option while sharing the details.

Regards,
Nikisha Patel, Google Ads API Team



ref:_00D1U1174p._5001USwglx:ref

Nick

unread,
Jan 18, 2020, 4:33:37 PM1/18/20
to AdWords API and Google Ads API Forum
Thanks for reaching out.
Was able to trace it back to an intermittent network error with our server and overseas traffic.

Issue is now resolved after contacting them.

Thank you.
Reply all
Reply to author
Forward
0 new messages