429 Resource has been exhausted

[Myeonggeun Ji]

Hi team,

I am getting error "429 Resource has been exhausted (e.g. check quota)." when calling search_stream method.

I looked into this error in the forum.

1. In common case, this error occurs when sending too many requests in short period of time.

or 

2. Search quota is 15k requests per user per day.

I think i'm not exceeding search quota, because retry request works well.

And i've been sending requests with backoff delay (1 sec).

To avoid error, do i need to increase backoff delay? And how much ?

RequestId: T7iyLJ7L5MSkWAjvZsdiPQ

Thanks,

[Google Ads API Forum Advisor]

Hi,

Thanks for reaching out to the Google Ads API Forum.

Since you received “FaultMessage: Resource has been exhausted (e.g. check quota).” error,  you may try to avoid sending too many requests in a short period of time. The server throws this error once it detects that your request has exceeded the system frequency limit. 

That being said, I would recommend setting up short delays between requests or combine more operations in fewer requests. Also, 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.

Also, 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.

In addition, please refer to the Best practices guide to optimize the efficiency and performance. Furthermore, you can consider throttling QPS from the client side (check out Throttling and rate limiters). 

I hope this helps.

Regards,

Yasar Google Ads API Team

ref:_00D1U1174p._5004Q2eNm8V:ref