Re: too many 429 error these days

2023-11-15 Thread Nick
Exact same thing happening to me. 

Was working perfectly for months, then all of a sudden 429 errors on more 
than 50% of requests. 

I know for a fact that I didn't exceed the 1 QPS or 15k/day quota bc I was 
getting 429 on the first request in a 24hr period. 

Got a similar response from Google, provided all the necessary logs then 
never heard back. 

Hoping they get it figured out. 

On Wednesday, November 15, 2023 at 10:36:17 AM UTC-5 Google Ads API Forum 
Advisor wrote:

> Hi,
>
> Thank you for reaching out to the Google Ads API support team.
>
> By reviewing your query, I understand that you are getting the error "
> RESOURCE_EXHAUSTED 
> ",
>  
> which means that a system frequency limit has been exceeded. Kindly prevent 
> sending too many requests in a short period of time and also ensure to set 
> up short delays between requests or combine more operations in fewer 
> requests. Also, please check this sample code for how to Handle a Rate 
> Exceeded Error 
> 
>  for 
> more information.
>
> Additionally, we also have daily API operation limits where requests that 
> violate these limits are rejected with the error: RESOURCE_EXHAUSTED. You 
> may check out API Limits and Quotas 
>  for 
> more information.
>
> If you are still encountering an error, kindly provide us with the updated 
> complete API logs (request 
> 
>  and response 
> 
>  with request-id 
> 
>  and request header 
> )
>  
> generated at your end to assist you better.
>
> If you are using a client library and haven't enabled the logging yet, I 
> would request you to enable logging for the specific client library that 
> you are using. You can refer to the guides Java 
> 
> , .Net 
> 
> , PHP 
> 
> , Python 
> 
> , Ruby 
> 
>  or Perl 
>  
> to 
> enable logging at your end. For REST interface requests, you can enable 
> logging via the curl command by using the -i flag.
>
> You can send the details via *Reply privately to the author option*, or 
> *direct 
> private reply* to this email.
>   
> This message is in relation to case "ref:!00D1U01174p.!5004Q02qCPUk:ref"
>
> Thanks,
>   
> [image: Google Logo] Google Ads API Team 
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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+unsubscr...@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 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/74a15bd7-df9b-4a82-9bf0-9aa370b7d64dn%40googlegroups.com.


RE: too many 429 error these days

2023-11-15 Thread 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
Hi,

Thank you for reaching out to the Google Ads API support team.

By reviewing your query, I understand that you are getting the error 
"RESOURCE_EXHAUSTED", which means that a system frequency limit has been 
exceeded. Kindly prevent sending too many requests in a short period of time 
and also ensure to set up short delays between requests or combine more 
operations in fewer requests. Also, please check this sample code for how to 
Handle a Rate Exceeded Error for more information.

Additionally, we also have daily API operation limits where requests that 
violate these limits are rejected with the error: RESOURCE_EXHAUSTED. You may 
check out API Limits and Quotas for more information.

If you are still encountering an error, kindly provide us with the updated 
complete API logs (request and response with request-id and request header) 
generated at your end to assist you better.

If you are using a client library and haven't enabled the logging yet, I would 
request you to enable logging for the specific client library that you are 
using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to 
enable logging at your end. For REST interface requests, you can enable logging 
via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct 
private reply to this email.
This message is in relation to case "ref:!00D1U01174p.!5004Q02qCPUk:ref"

Thanks,

Google Ads API Team

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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+unsubscr...@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 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/4F3p00S468NP00a2NiQHSCTbOsE8E7IT8ZzQ%40sfdc.net.