Custom report timing out

[Adrian Pell]

I have a strange case where one report that we request through the API never returns a response.  That is, no matter how long we leave it, there is never a response to the HTTP POST containing the report spec.

Looking at some earlier discussion, there was talk about timeouts - which indicated that these should not be necessary since we should either get the requested data, or an Adwords error to which we can respond in some appropriate way (reduce scope, segments, etc.)  I get neither.

The report in question is a Geo Performance Report, segmented by Campaign, Month, City ... which is probably quite large, but I would still expect a response.  We have some other pretty large reports with similar specs (although for different accounts) which succeed.

Any ideas what might be going on?  I'm quite happy to split the report up further ... but I don't want to do that unless necessary, since every other similar report succeeds.

BTW - setting a Timeout in the .NET API (the default is indefinite) causes a different problem which I've logged an issue for in Github.

Thanks

Adrian

BTW - I'm using the latest 18.22.0 version of the .NET API although still with the v201509 version of the protocol.

[Yin Niu]

Hi Adrian, 

Could you please provide me with the report definition you used and your client customer Id, so that the team can further investigate this issue? Please click Reply privately to author when responding. 

Thanks,

Yin, AdWords API Team.