Re: Read timed out on API calls

Hi Thomas, Stefan, Glad to hear that the problem has gone. I'm still following up with engineering and also doesn't have clue what happened. If I get more information, I will keep you posted. Best, Thanet, AdWords API team On Monday, September 19, 2016 at 6:02:56 PM UTC+9, Tomas Rimkus wrote: >

Re: Read timed out on API calls

It seems to be working well for us too since Friday. It would be nice if google developers could share what was the problem on their end which caused the timeouts. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.co

Re: Read timed out on API calls

Hi Thanet, just wanted to report that the timeout problems have gone now. Timeouts started to drop significantly on friday morning and since saturday, we don't any have timeout at all. Just out of interest: did you change anything on your side? Anyway, thanks for your support. Stefan Am Mit

Re: Read timed out on API calls

Hello Christian, Stefan, Thanks for information. I'll pass this to engineering for more investigation. Cheers, Thanet, AdWords API Team On Wednesday, September 14, 2016 at 12:27:16 AM UTC+9, Christian wrote: > > Hi, > > we are in AWS Frankfurt as well. Could be relevant: we are use AWS' > manag

Re: Read timed out on API calls

Hi, we are in AWS Frankfurt as well. Could be relevant: we are use AWS' managed NAT service. Best, Christian On Tuesday, September 13, 2016 at 5:08:03 PM UTC+2, Stefan Kleine Stegemann wrote: > > > Hi Josh, > > sorry for the second post but I did not read it completely first. > > The failed re

Re: Read timed out on API calls

Hi Josh, sorry for the second post but I did not read it completely first. The failed request was also retried on our side and went through without problems (definitely less than 4 minutes). Thanks, Stefan Am Dienstag, 13. September 2016 16:34:46 UTC+2 schrieb Josh Radcliff (AdWords API Tea

Re: Read timed out on API calls

Hi Josh, we're also running on AWS services located in Frankfurt, Germany. Stefan Am Dienstag, 13. September 2016 16:34:46 UTC+2 schrieb Josh Radcliff (AdWords API Team): > > Hi Stefan, > > Thanks for sending over the details of your reporting request. What's odd > is that I ran that same re

Re: Read timed out on API calls

We are running Amazon EC2 instance located in Frankfurt, Germany. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=

Re: Read timed out on API calls

Hi Stefan, Thanks for sending over the details of your reporting request. What's odd is that I ran that same request and it returned in ~4 minutes. *Everyone who is watching this thread:* Could you let me know which region or country your hosts reside in, provided you are comfortable sharing th

Re: Read timed out on API calls

Hi Josh, as an additional information, our main problem seems to be the AdWords management API, not the reporting API. The latter is giving us timeouts as well but we are usually talking "only" about minutes here. The main problem are the services (TrafficEstimatorService, CampaignService, AdG

Re: Read timed out on API calls

I can confirm that the issue is still present. At least one report download failed after multiple retries due to read time-out on our end. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.co

Re: Read timed out on API calls

Hi Josh, is there any update on this issue? The situation is still the same and we haven't noticed an improvement over the past days (it also did not get worse, though). Thanks, Stefan Am Freitag, 9. September 2016 19:49:14 UTC+2 schrieb Josh Radcliff (AdWords API Team): > > Hi Stefan, > >

Re: Read timed out on API calls

For anyone following this, here is the cleaned up version of a private mail I sent to Josh: Hi Josh, we now also have some details about a failing request. While most API calls hang randomly (approx. 1 of 20), we have a reliably failing call on the account XYZ when downloading a report. Starting

Re: Read timed out on API calls

Hi Stefan, Thanks for sending over that info. I looked at those requests and didn't see any errors in terms of AdWords API handling, which suggests this may be an issue at a different layer on our side. I'll keep digging and let you know what I find. Cheers, Josh, AdWords API Team On Friday,

Re: Read timed out on API calls

Hi Josh, I sent you a private mail with some information. I hope that helps. Thanks, Stefan Am Freitag, 9. September 2016 15:58:01 UTC+2 schrieb Josh Radcliff (AdWords API Team): > > Hi Stefan, > > Thanks for looking. Since you aren't getting a response back due to the > timeout, you won't

Re: Read timed out on API calls

Hi Stefan, Thanks for looking. Since you aren't getting a response back due to the timeout, you won't have a *requestId* (which is part of the response payload). However, if you have a specific ad group ID or campaign ID where you've encountered timeouts, along with the timestamp (including tim

Re: Read timed out on API calls

Hi Josh, i'm sorry but I wasn't able to find a request with a request-id in our logs. I inspected the soap dumps from failed requests and found none with a request id. I found some other failed requests where the id was displayed but these requests failed because of "normal" errors (such as us

Re: Read timed out on API calls

Hi, We are experiencing exactly the same problem since 7th of September when using Reporting API. It seems the time-outs occur for some accounts more often than the others. It's also taking way too long for the connection to be dropped because of "time-out" with default settings. How can we set

Re: Read timed out on API calls

Hi, we are using the Python client library. Looks like there is a default timeout of 1 hour for SOAP (suds) requests, but in practice the hanging reads on connections do not time out. I'll check for a unique request identifier as well and will forward it to you, Josh. Best, Christian --- Christ

Re: Read timed out on API calls

Hi Josh, thanks for your reply. First, the situation got much worse this morning with the number of timeouts increasing significantly. About setting the read timeout, is there a away of doing that in pure Java without ads.properties because we have our own "setup code" and configuration mecha

Re: Read timed out on API calls

Hi, Would either of you happen to have a particularly unique example request where this failed? It looks like you're not getting back a *requestId* in this case, but if your request contained a string or ID that was unique to that request, that would help me track down what happened. If you wo

Re: Read timed out on API calls

Hi, One other tip: if you're encountering this issue with reporting requests and using the Java client library, you can modify the api.adwords.reportDownloadTimeout value

Re: Read timed out on API calls

Hi, I'll look into the increased occurrences of timeouts, but in the meantime, if you are using the Java client library, you can reduce the SOAP request timeout from the default of 20 minutes (120 milliseconds) by setting the api.adwords.soapRequestTimeout value in your ads.properties file

Re: Read timed out on API calls

Hi, we got similar problems starting September 6, 3pm UTC. Since then an increased number of API calls hang when reading from a socket (we read in blocking mode from sockets). For now the connections seem to be held open indefinitely. I would expect it to be closed by some Google server sooner

Read timed out on API calls

Hi, over the past days, we experienced an increasing number of read-timeouts when making API calls. The timeouts are not restricted to a specific service but we have observed them for CampaignService, TrafficEstimatorService, Reporting and some others . I seems that our network is not the pro