Google Ads API Error – ResourceExhausted Exception When Running GAQL Query

28 views
Skip to first unread message

teamvadw...@gmail.com

unread,
Oct 21, 2025, 9:38:57 AM10/21/25
to Google Ads API and AdWords API Forum
Hi Team,
 
I am reaching out for assistance regarding a recurring exception encountered when executing a GAQL query through the Google Ads API. We have observed that the issue is not related to excessive or unusual daily resource usage on our end. The exception occurs within just a few executions from our environment, and the quota appears to reset the following day. Despite minimal usage, the API intermittently returns the error noted below, which is preventing us from running our queries consistently.

Please find below example Account Details:
Paragon Honda --> 127-167-0580

Issue Summary

While running the following GAQL query, the Google Ads API returns a ResourceExhausted exception:

SELECT campaign.id, campaign.name, campaign.status, campaign.end_date, campaign_budget.id, campaign.advertising_channel_type, campaign_budget.amount_micros, campaign.geo_target_type_setting.negative_geo_target_type, campaign.geo_target_type_setting.positive_geo_target_type, campaign.bidding_strategy_type FROM campaign WHERE campaign.status IN ('ENABLED', 'PAUSED')

Exception Details
Status(StatusCode="ResourceExhausted", Detail="Resource has been exhausted (e.g. check quota).", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1761050016.088000000", "description":"Error received from peer ipv4:142.251.111.95:443", "file":"..\..\..\src\core\lib\surface\call.cc","file_line":953, "grpc_message":"Resource has been exhausted (e.g. check quota).", "grpc_status":8}")

Request

Could you please help us identify the root cause and advise on the next steps? Specifically, we would like to know:

  1. Whether this is related to API quota limits or resource usage.

  2. If there are recommended best practices (pagination, throttling, etc.) to avoid this exception.

  3. Whether any quota increases are required on our account.


Additional Notes
  • The query is a simple campaign-level fetch and we are only filtering by campaign status.

  • We would like to continue running this query at scale without hitting resource limits.


Please let us know if you need our customer ID, request logs, or any additional details to investigate further.


Regards,

TeamvAds

Google Ads API Forum Advisor

unread,
Oct 21, 2025, 5:19:47 PM10/21/25
to teamvadw...@gmail.com, adwor...@googlegroups.com
Hi,

Thank you for reaching out to the Google Ads API support team. 

From the provided information, I understand that you are experiencing the RESOURCE_EXHAUSTED error. The RESOURCE_EXHAUSTED error generally occurs when you are sending too many requests in a short period of time. The server displays this error once it detects that your request has exceeded the system frequency limit. I would recommend giving short delays between requests or combining more operations in fewer requests. 


Whether this is related to API quota limits or resource usage.

Kindly note that basic access allows the developer token to execute up to 15,000 operations per day. This is sufficient for most developers. Standard access allows the developer token to execute unlimited number of operations per day for most services. You can fill out the standard access application form to apply for the standard access. I would recommend you refer to this guide on "Access levels and permissible use" for more information.


If there are recommended best practices (pagination, throttling, etc.) to avoid this exception.

Kindly refer to this guide for more information.


Whether any quota increases are required on our account.

As suggested above, you may get standard access to execute unlimited number of operations per day for most services.

Hope this helps. If you have any more queries, please feel free to get back to us.

Thanks,
 
Google Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-10-21 21:19:06Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vRN02:ref" (ADR-00336102)



Reply all
Reply to author
Forward
0 new messages