Hi, 

We have verified that the issue is not driven by gRPC client message limits 
in our code as our code uses streaming and mutates are using 1-2 operations 
per request. Regardless, when we receive these 429 errors we are 
subsequently locked out of our account for anywhere from 12-24 hours even 
though we have verified that this is below the published quota limits. 

Can you please look into this for us?


Thanks!

On Sunday, September 25, 2022 at 9:53:22 PM UTC-4 adsapi wrote:

> Hi George,
>
> Thank you for posting your concern.
>
> With regard to your concern, it appears that it is not related with the 
> daily operational limit of the basic access developer token that you have. 
> It is related to what was discussed in this document 
> <https://developers.google.com/google-ads/api/docs/best-practices/quotas#grpc_limitations>
>  that 
> "*All of the Google Ads API client libraries 
> <https://developers.google.com/google-ads/api/docs/client-libs> use gRPC 
> <https://grpc.io/> for generating requests and responses. By default, gRPC 
> has a message size of 4 MB, but our client libraries set the max message 
> size to 64 MB in order to increase efficiency.* 
>
> *Responses must not exceed this limit. For example, a search request that 
> includes a lot of fields may generate a response that exceeds 64 MB in 
> size. To avoid this limit, you can reduce the number of selected fields, 
> reduce the page size, or use streaming 
> <https://developers.google.com/google-ads/api/docs/reporting/streaming>. 
> For mutates, send fewer operations per request.*
>
> *Requests that violate this limitation will not generate a GoogleAdsError 
> <https://developers.google.com/google-ads/api/reference/rpc/v11/GoogleAdsError>,
>  
> but will generate a 429 Resource Exhausted gRPC error. Refer to the list of 
> gRPC error codes and messages 
> <https://github.com/grpc/grpc/blob/master/doc/statuscodes.md>.*"
> You may follow the suggestions provided above to address the issue. If you 
> have any questions, do not hesitate to reach out again and our team will be 
> happy to provide support.
>
> Regards,
> [image: Google Logo] 
> Ernie John 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2efS4P:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/7a895765-8845-4f5b-8bca-d0656c6ab288n%40googlegroups.com.
  • 42... Sprighub Ads
    • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
    • ... Myeonggeun Ji
    • ... George Lin
      • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
        • ... George Lin
          • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to