Hi Christian,
Thanks for getting back to us.
Could you confirm if you’re using our supported client library and encountering
DEADLINE_EXCEEDED error? If yes, you may try not using proto-plus. Does it help
if you switch to the non-proto-plus interface described in our docs for slower
requests o
Hi Heidi,
that's what I'm already doing if possible: I select only the ads of
specified adgroups. But in some cases I have to load all ads of the
accounts and splitting up the request is really unhandy. In my opinion
there is a performance issue/bug on your side. The reasons why I believe
this
Hi Christian,
Thank you for reaching out to us.
You may note that timeouts are often because what is being queried is too big
to send back to you. It appears that those accounts where this is failing
contain a lot of data. To fix this deadline exceeded error you are
encountering, I would sugge
Hi!
I have the same problem: downloading RSAs takes too long (for some
accounts). I run into the DEADLINE_EXCEEDED exception too (And I set the
timeout to 20 minutes which should be more than sufficient).
There is a workaround: if I request headlines and descriptions with
different requests th
Hi Gavin,
Thank you for reaching out to us.
The DEADLINE_EXCEEDED error occurs when the request took longer than a deadline.
But since you said that “The query can successfully return ~400k Responsive
Search Ads within 40 minutes. But now it hit the "Deadline Exceeded" every 15
minutes” even t
Hello,
We noticed that starting from this Wednesday, lots of RPC exceptions with
"Deadline Exceeded" started to show up in the queries for Responsive Search
Ads. Those queries that we sent to Google Ads API may return large amount
of Responsive Search Ads but there was no such problem at all wh
