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 Mittwoch, 14. September 2016 10:53:02 UTC+2 schrieb Thanet Knack Praneenararat (AdWords API Team):

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' 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 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 Team):

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 that information? I'd like to know if this is limited to a specific region, or if region is not a factor. If you'd prefer to share that information only with me, you can click Reply privately to author on this message.

Thanks,

Josh, AdWords API Team

On Tuesday, September 13, 2016 at 7:12:06 AM UTC-4, Stefan Kleine Stegemann wrote:

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, AdGroupService) which have very long timeouts (up to an hour, as I've mentioned in my first post).

Cheers,

Stefan

Am Freitag, 9. September 2016 19:49:14 UTC+2 schrieb Josh Radcliff (AdWords API Team):

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, September 9, 2016 at 10:31:58 AM UTC-4, Stefan Kleine Stegemann wrote:

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 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 timezone) of the timed out request, I may be able to find what went wrong with that particular request.

Thanks,

Josh, AdWords API Team

On Friday, September 9, 2016 at 7:27:56 AM UTC-4, Stefan Kleine Stegemann wrote:

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 user permission denied). I wonder what's the rule for request having an id or not?

Cheers,

Stefan

Am Donnerstag, 8. September 2016 23:41:27 UTC+2 schrieb Josh Radcliff (AdWords API Team):

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 would prefer, you can send the information only to me by clicking Reply privately to author on this message.

Thanks,

Josh, AdWords API Team

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups "AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/b46987c3-e6a2-410a-89ae-c78268ef2865%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.