Hi Anash, just wanted to follow up -- I believe I privately replied with my
manager account id / email. Google Groups doesn't seem to have a view for
private replies, so just wanted to make sure it got to you. If not, please
let me know if there is an email or other way to pass along the info.
Appreciate it! Apologies for the confusion on the versioning -- the docs
mentioned a v18
`QuotaError.EXCESSIVE_SHORT_TERM_QUERY_RESOURCE_CONSUMPTION,` so I assumed
it was available.
On Wednesday, June 26, 2024 at 11:12:26 AM UTC-7 Google Ads API Forum
Advisor wrote:
> Levi:
>
> Did you mean v
Thanks for the update Bob -- could you please clarify the new v18 search
rate limits mentioned above
(https://ads-developers.googleblog.com/2024/05/google-ads-api-resource-usage-policy.html)?
After digging through available resources, I have a couple of
concerns/questions:
1. What are the act
Working again for me now.
On Wednesday, June 26, 2024 at 6:46:08 PM UTC+1 Matt Dworkin wrote:
> In the logs I'm seeing that a retry needs to wait 900 seconds, so I'm not
> sure exponential backoff will help. Could that actually end up hurting?
> Does the "retry time" reset if we send another re
In the logs I'm seeing that a retry needs to wait 900 seconds, so I'm not
sure exponential backoff will help. Could that actually end up hurting?
Does the "retry time" reset if we send another request before 15 minutes
has passed?
On Wednesday, June 26, 2024 at 1:41:32 PM UTC-4 Google Ads API F
The same situation continues for me. However, I thought the problem was
related to new query limits. I hope it is a general problem and gets solved.
26 Haziran 2024 Çarşamba tarihinde saat 20:27:48 UTC+3 itibarıyla Levi
Kline şunları yazdı:
> Interesting -- I was not aware of this breaking chan
Interesting -- I was not aware of this breaking change. It also seems as
though they haven't even added these new v18 errors to protobuf.
On Wednesday, June 26, 2024 at 10:04:55 AM UTC-7 Alex Black wrote:
> We're being significantly impacted too, I assume this is a result of
> https://ads-devel
+1 same issue here
On Wednesday, June 26, 2024 at 10:05:15 AM UTC-7 James Guiden wrote:
> +1
>
> Experiencing similar difficulties. API requests made to searchStream are
> left hanging, with occasional 429 RESOURCE_EXHAUSTED error messages being
> returned (for a single API call, not exceeding
+1
Experiencing similar difficulties. API requests made to searchStream are
left hanging, with occasional 429 RESOURCE_EXHAUSTED error messages being
returned (for a single API call, not exceeding our quota limit).
On Wednesday, June 26, 2024 at 12:29:00 PM UTC-4 GDZ wrote:
> We have an unli
+1 Same issue across many accounts. Current automated API jobs (for tasks
like offline conversion upload) succeed for a few requests before timing
out with RESOURCE_EXHAUSTED errors.
On Wednesday, June 26, 2024 at 11:29:00 AM UTC-5 GDZ wrote:
> We have an unlimited quota. Why all this RESOURCE_
We are having the same issue starting this morning: RESOURCE_EXHAUSTED on
many requests. We have the Standard access level with unlimited quota. We
have hundreds of campaigns pending important updates that we can't process
because of this.
On Wednesday, June 26, 2024 at 11:55:26 AM UTC-4 Levi
+1, is there any issue?
在2024年6月26日星期三 UTC+8 23:55:26 写道：
> +1 Same issue
>
> On Wednesday, June 26, 2024 at 8:52:06 AM UTC-7 ro...@searchkings.ca
> wrote:
>
>> Same -- glad to know it's not just us!
>>
>> On Wednesday, June 26, 2024 at 11:44:33 AM UTC-4 Matteo Medda wrote:
>>
>>> We are seeing
We are experiencing the same issue
On Wednesday, June 26, 2024 at 5:13:57 PM UTC+2 Zorion wrote:
> Same here. The API is unusable in those conditions.
>
> On Wednesday, June 26, 2024 at 5:03:01 PM UTC+2 Sergei Aleinik wrote:
>
>> I confirm. Same problems
>>
>> среда, 26 июня 2024 г. в 16:50:45 UT
We're being significantly impacted too, I assume this is a result
of
https://ads-developers.googleblog.com/2024/05/google-ads-api-resource-usage-policy.html
?
It'd help to get a quota increase, even a temporary one!
On Wednesday, June 26, 2024 at 8:52:06 AM UTC-7 ro...@searchkings.ca wrote:
Same issue. We see some "RESOURCE_EXHAUSTED" but also so many unexplained
timeouts and delays everywhere.
On Wednesday, June 26, 2024 at 5:13:57 PM UTC+2 Zorion wrote:
> Same here. The API is unusable in those conditions.
>
> On Wednesday, June 26, 2024 at 5:03:01 PM UTC+2 Sergei Aleinik wrote:
Same problem here
On Wednesday, June 26, 2024 at 4:13:57 PM UTC+1 Zorion wrote:
> Same here. The API is unusable in those conditions.
>
> On Wednesday, June 26, 2024 at 5:03:01 PM UTC+2 Sergei Aleinik wrote:
>
>> I confirm. Same problems
>>
>> среда, 26 июня 2024 г. в 16:50:45 UTC+2, Radosław Poc
We have an unlimited quota. Why all this RESOURCE_EXHAUSTED errors all of a
sudden? We had to pause campaigns in hundreds of different accounts. Needs
to be fixed ASAP!
On Wednesday, June 26, 2024 at 10:28:36 AM UTC-4 Haritha Devalla wrote:
> Hi Team,
>
> We are facing high latency with the AP
+1 Same issue
On Wednesday, June 26, 2024 at 8:55:26 AM UTC-7 Levi Kline wrote:
> +1 Same issue
>
> On Wednesday, June 26, 2024 at 8:52:06 AM UTC-7 ro...@searchkings.ca
> wrote:
>
>> Same -- glad to know it's not just us!
>>
>> On Wednesday, June 26, 2024 at 11:44:33 AM UTC-4 Matteo Medda wrote:
+1 Same issue
On Wednesday, June 26, 2024 at 8:52:06 AM UTC-7 ro...@searchkings.ca wrote:
> Same -- glad to know it's not just us!
>
> On Wednesday, June 26, 2024 at 11:44:33 AM UTC-4 Matteo Medda wrote:
>
>> We are seeing the same behaviour from today.
>>
>> On Wednesday 26 June 2024 at 17:39:51
Same -- glad to know it's not just us!
On Wednesday, June 26, 2024 at 11:44:33 AM UTC-4 Matteo Medda wrote:
> We are seeing the same behaviour from today.
>
> On Wednesday 26 June 2024 at 17:39:51 UTC+2 Matt Dworkin wrote:
>
>> We're also having the same issues. First it was Bad Gateways, now
>>
We are seeing the same behaviour from today.
On Wednesday 26 June 2024 at 17:39:51 UTC+2 Matt Dworkin wrote:
> We're also having the same issues. First it was Bad Gateways, now
> RESOURCE_EXHAUSTED. We supposedly have an unlimited quote so it's not clear
> why we would have these RESOURCE_EXHAU
Same situation, we are receiving a lot of random RESOURCE_EXHAUSTED error
on multiple different accounts
Il giorno mercoledì 26 giugno 2024 alle 17:39:51 UTC+2 Matt Dworkin ha
scritto:
> We're also having the same issues. First it was Bad Gateways, now
> RESOURCE_EXHAUSTED. We supposedly have
We're also having the same issues. First it was Bad Gateways, now
RESOURCE_EXHAUSTED. We supposedly have an unlimited quote so it's not clear
why we would have these RESOURCE_EXHAUSTED issues
On Wednesday, June 26, 2024 at 11:37:35 AM UTC-4 Richard Cutting wrote:
>
> Same here also seeing a lot
Same here also seeing a lot of RESOURCE_EXHAUSTED errors and I know we
haven't !
On Wednesday, June 26, 2024 at 3:50:45 PM UTC+1 Radosław Pociecha wrote:
> We are seeing the same behaviour.
>
> On Wednesday, June 26, 2024 at 4:34:57 PM UTC+2 Jing CHEN wrote:
>
>> The same situation.
>>
>> 在2024年
Same here. The API is unusable in those conditions.
On Wednesday, June 26, 2024 at 5:03:01 PM UTC+2 Sergei Aleinik wrote:
> I confirm. Same problems
>
> среда, 26 июня 2024 г. в 16:50:45 UTC+2, Radosław Pociecha:
>
>> We are seeing the same behaviour.
>>
>> On Wednesday, June 26, 2024 at 4:34:57
I confirm. Same problems
среда, 26 июня 2024 г. в 16:50:45 UTC+2, Radosław Pociecha:
> We are seeing the same behaviour.
>
> On Wednesday, June 26, 2024 at 4:34:57 PM UTC+2 Jing CHEN wrote:
>
>> The same situation.
>>
>> 在2024年6月26日星期三 UTC+8 22:28:36 写道：
>>
>>> Hi Team,
>>>
>>> We are facing hi
We are seeing the same behaviour.
On Wednesday, June 26, 2024 at 4:34:57 PM UTC+2 Jing CHEN wrote:
> The same situation.
>
> 在2024年6月26日星期三 UTC+8 22:28:36 写道：
>
>> Hi Team,
>>
>> We are facing high latency with the API calls and are also seeing
>> deadline exceeded errors for most of the accoun
The same situation.
在2024年6月26日星期三 UTC+8 22:28:36 写道：
> Hi Team,
>
> We are facing high latency with the API calls and are also seeing deadline
> exceeded errors for most of the accounts for the past two hours.
> Could you please look into this at the earliest and let us know if there
> is an
28 matches
Mail list logo
