Inquiry About Google Ads API Rate Limit Behavior (Retry in 66497 seconds)

[yuta]

Dear Google Ads API Support Team,

We hope this message finds you well.
We are currently using the Google Ads API in our production environment.

We are encountering the following error, mainly when querying Search Query data (search_term_view):

Too many requests. Retry in 66497 seconds.

After reviewing the Google Cloud Console,
we understand that one of the applicable rate limits was exceeded at the time this error occurred.

However, once this error is triggered, all API requests are completely blocked for more than 18 hours,
which stops our reporting and automation processes and causes a significant impact on our business operations.

To better understand and mitigate this issue, we would appreciate clarification on the following points:

1. Which specific rate limit caused this error
   (e.g. per-minute, per-hour, per-customer, or search_term_view–specific limits)

2. The conditions and specifications under which such a long retry duration
   (Retry in 66497 seconds) is applied

3. How request cost is calculated for search_term_view,
   and whether this resource has stricter limitations than others

4. Recommended best practices to avoid triggering this behavior
   (such as request intervals, GAQL partitioning, or throttling strategies)

5. Whether quota adjustments, rate limit relaxation, or developer-token–level mitigation
   can be considered given the operational impact

Please note that our API calls are executed sequentially, not in burst or highly concurrent mode.

While we understand the necessity of rate limits,
we would appreciate guidance on how to design our usage so that long-term full blocking can be avoided.

Thank you very much for your time and support.

Kind regards,