Re: Google Ads API V19 not working without keeping delay between API calls.

51 views
Skip to first unread message
Message has been deleted

Google Ads API and AdWords API Forum

unread,
Jun 13, 2025, 1:49:50 AMJun 13
to Google Ads API and AdWords API Forum
Hi Jayasimha, 

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

Please be informed that I have removed your response from the forums as it contains the PII information. 

Based on the information provided, I understand that you are encountering the RESOURCE_EXHAUSTED error while making the Google Ads API calls. 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. Also, please refer to the “Batch operations” documentation for more information. Additionally, you may refer to the "Usage flow" guide for insights on incorporating batch processing into your API requests. The Google Ads API enforces limits on API operations, such as the number of operations that can be sent to a single mutate request. I would recommend you to kindly refer to the API Limits and Quotas documentation for more information. 

Based on the error message, I could see that your developer token is having basic access. Also, this error may occur if you have already exceeded the daily limit of 15,000 API operations per day. Kindly note that the "RESOURCE_EXHAUSTED" error can be mitigated by increasing the number of operations per day. If you would like to apply for unlimited Google Ads API operations, fill out the standard access application form. I would suggest you please refer to this “Access Levels and Permissible Use” documentation for more information.


Thanks & Regards,

Google Ads API Team


On Thursday, June 12, 2025 at 5:03:02 PM UTC+5:30 market....@in.abb.com wrote:
Hi Team,

We are pulling the data through Google ads api and which was working fine from last one year. However, We have recently migrated the Google ads version from V17 to V19 as the V17 was deprecated.


Previously, The entire load was taking around 5 hours to complete. Now the load is taking more than 24 hours and it is failing with below issue.


Steps taken:

Previously, We were calling API's in parallel while requesting the data for Campaigns, Campaign groups, AdGroup data etc. But after migrating the version I have changed the API calls in series and gave the wait time as 2 mins in between each API request. Please let me know what is the minimum wait time between each API call? And how we can reduce the run time.


Operation on target ForEach1 failed: Activity failed because an inner activity failed; Inner activity name: AdgroupDataCY, Error: ErrorCode=GenericAdoNetConnectionOpenError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Failed to open the database connection.,Source=Microsoft.DataTransfer.Connectors.GenericAdoNet,''Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The http call failed with client error, status code 429 429, please check your activity settings.

Response: {

 "error": {

   "code": 429,

   "message": "Resource has been exhausted (e.g. check quota).",

   "status": "RESOURCE_EXHAUSTED",

   "details": [

     {

       "@type": "type.googleapis.com/google.ads.googleads.v19.errors.GoogleAdsFailure",

       "errors": [

         {

           "errorCode": {

             "quotaError": "RESOURCE_EXHAUSTED"

           },

           "message": "Too many requests. Retry in 18023 seconds.",

           "details": {

             "quotaErrorDetails": {

               "rateScope": "DEVELOPER",

               "rateName": "Get request for basic access",

               "retryDelay": "18023s"

             }

           }

         }

       ],

       "requestId": "M1x6XfdE5CIFzoND4iCj3A"

     }

   ]

 }

}

,Source=Microsoft.DataTransfer.Connectors.GoogleAds,'


Regards,

Jayasimha

Reply all
Reply to author
Forward
0 new messages