Hi Aaron,

I work with Nirmita. Thanks for getting back to us.

I understand that you have encountered an RESOURCE_EXHAUSTED error, and error 
message ‘Too many requests. Retry in 900 seconds“. This seems to be that API 
requests hitting the server aggressively. The server throws this error once it 
detects that your request has exceeded the system frequency limit. When you 
retry requests, you may continue using an exponential backoff policy by 
delaying 5-10 seconds. For example, if you first pause 5 seconds before the 
first retry, you could pause 10 seconds after the second and 20 seconds after 
the third retry. Exponential backoff helps ensure you are not calling the API 
too aggressively.

Also, you mentioned that you set your batch job hourly to process sync campaign 
data from Google Platform, but in the above email you provided error logs for 
the GoogleAdsService/SearchStream API request. So, there seems to be concurrent 
API requests making calls to Google Ads API at same time, and this is why you 
encountered said error.

That being said, we suggest setting a reasonable upper bound for the total 
number of concurrent tasks that are going to make requests (across all 
processes and machines), and adjusting upward to optimize your throughput 
without exceeding the rate limit is recommended. Otherwise, you may possibly 
experience the exceeding rate limits that the client app is spawning an 
excessive number of parallel tasks since we don't limit the number of parallel 
requests a client app can have, this can easily exceed the Requests Per Second 
limit at the developer token level. However, Throttles can be implemented at 
the consumer side by limiting the number of concurrent consumers, or implement 
rate limiters or throttlers for either the producers or consumers.For more 
information, you may refer to this throttling QPS from the client side (check 
out Throttling and rate limiters).

You may apply above mentioned points while sending requests to Google Ads API 
server, and let us know how this goes on.

Regards,

Yasar
Google Ads API Team
ref:_00D1U1174p._5004Q2gQH50: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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/VlcNq000000000000000000000000000000000000000000000RN6DNQ00ZLKB21GKS3yQt2j8ybVbQw%40sfdc.net.
  • IN... 'changhong yun' via Google Ads API and AdWords API Forum
    • ... Google Ads API and AdWords API Forum
      • ... 'changhong yun' via Google Ads API and AdWords API Forum
        • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
          • ... 'changhong yun' via Google Ads API and AdWords API Forum
            • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
              • ... 'changhong yun' via Google Ads API and AdWords API Forum
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
                • ... 'changhong yun' via Google Ads API and AdWords API Forum
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
                • ... 'changhong yun' via Google Ads API and AdWords API Forum
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
                • ... 'changhong yun' via Google Ads API and AdWords API Forum

Reply via email to