I wrote it to handle QuotaErrorEnum.QuotaError when I had dozens of concurrent processes hitting your API and your API getting very upset that the other process stacks kept sending API requests, but that said, it's not a request for help but instead help for those who may be in a similar situation.
On Tue, 1 Aug 2023 at 13:56, Google Ads API Forum Advisor <adsapi@forumsupport.google> wrote: > Hi, > > Thank you for reaching out to the Google Ads API support team. > > Regarding your concern, please note that our team provides assistance to > concerns or issues related to *Google Ads API* ( > https://developers.google.com/google-ads/api/docs/start). Having said > that, can you confirm if this is related to the Google Ads API? If so, can > you provide more context or details regarding this so our team can have a > better view and provide precise recommendations? > > If you are encountering Google Ads API-related errors, can you provide the > below complete API logs for investigation? > > - request - > > https://developers.google.com/google-ads/api/docs/concepts/field-service#request > - response - > > https://developers.google.com/google-ads/api/docs/concepts/field-service#response > - request ID - > > https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id > - request header - > > https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers > > > You may then send the requested logs via the *Reply privately to author > *option. > If this option is not available, you may send the details directly to our > googleadsapi-supp...@google.com alias instead. > > Moreover, since you mentioned that you're getting rate limit errors, > kindly note that the Google Ads API buckets requests for rate limiting by > queries per second (QPS) per client customer ID (CID) and developer token, > meaning that metering is enforced independently on both CIDs and developer > tokens. You may check our *Rate Limits* ( > https://developers.google.com/google-ads/api/docs/best-practices/rate-limits) > for more details. > > This message is in relation to case "ref:_00D1U1174p._5004Q2nZmEx: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/CAN%3DxSjPE9T%3DTKxv2VmkETo5vSfdavMUMOfngGNXnzt3JZGQuyA%40mail.gmail.com.
