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 Sep 8 we got a "connection reset by peer" error after waiting for some data for 2 hours. We then set a read timeout on the socket of 5 minutes, which now is exceeded whenever we want to download the particular report. We had some similar problems before on that account but eventually (after a few automatic retries) we usually could successfully download the report. That is not possible anymore.

The report is a PRODUCT_PARTITION_REPORT.

Thanks for investigating this issue.

Best,

Christian

---

Christian Bünnig
Head of Software Development

Bidmanagement GmbH | Chausseestraße 22 | D-10115 Berlin
T +49 30 4081715-500 | F +49 30 4081715-555
christian.buennig@adspert.de | http://www.adspert.de

Amtsgericht: Berlin-Charlottenburg 133120 B
Geschäftsführer: Marcel Pirlich, Stephanie Richter

On Mon, Sep 12, 2016 at 9:40 PM, Christian Bünnig <christian.buennig@adspert.de> wrote:

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 163-031-8785 when downloading a report. Starting Sep 8 we got a "connection reset by peer" error after waiting for some data for 2 hours. We then set a read timeout on the socket of 5 minutes, which now is exceeded whenever we want to download the particular report. We had some similar problems before on that account but eventually (after a few automatic retries) we usually could successfully download the report. That is not possible anymore.

The report is a PRODUCT_PARTITION_REPORT. Example time stamp when we tried to download that report: 2016-09-12 04:32:13 UTC.

Thanks for investigating this issue.

Best,

Christian

---

Christian Bünnig
Head of Software Development

Bidmanagement GmbH | Chausseestraße 22 | D-10115 Berlin
T +49 30 4081715-500 | F +49 30 4081715-555
christian.buennig@adspert.de | http://www.adspert.de

Amtsgericht: Berlin-Charlottenburg 133120 B
Geschäftsführer: Marcel Pirlich, Stephanie Richter

On Fri, Sep 9, 2016 at 7:49 PM, 'Josh Radcliff (AdWords API Team)' via AdWords API Forum <adwords-api@googlegroups.com> wrote:

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 a topic in the Google Groups "AdWords API Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adwords-api/OWusHGc6xaY/unsubscribe.
To unsubscribe from this group and all its topics, 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/c217fdb8-616f-4d2f-8153-8fc962ea24a0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/CAOitGrUk_-hpf6YB7mfygwY0pby-W4n9zt8Znr8F_FZ859fs6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.