Quota/Resource Exhausted when switching from .NET V14 to V15

[Mads Grout]

Hi

We are making the switch from .NET v14 library to v15 to accommodate the new consent status.

While doing this we encountered a problem.

Hour system uses the UserdataService.UploadUserDataAsync  to upload user data to customermatch lists.

Currently using the V14 library it is able to handle a lot of load. Like thousand UserIdentifiers a minute or more when we make concurrent calls.

When switching to the V15 library we suddenly just get the following error: 

"Status(StatusCode=\"ResourceExhausted\", Detail=\"Resource has been exhausted (e.g. check quota).\")"

I am quite familiar with all of the documentation and i don't need any of the basic answers pointing to what UserDataService was made for and what it can handle.

This solution has been working for well over a year now... And now when bumping to V15 i suddenly doesn't.

I'm trying to figure out why this happens... I can't seem to find anything regarding any Quota/Rate limiting changes in any release note, changelog or blog anywhere.

Is there any explanation for this??

[Google Ads API Forum Advisor]

Hi,

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

By reviewing your query, I understand that you are getting the "RESOURCE_EXHAUSTED", which means that a system frequency limit has been exceeded. Kindly prevent sending too many requests in a short period of time and also ensure to set up short delays between requests or combine more operations in fewer requests. Also, please check this sample code for how to Handle a Rate Exceeded Error for more information.

Additionally, we also have daily API operation limits where requests that violate these limits are rejected with the error: RESOURCE_EXHAUSTED. You may check out API Limits and Quotas for more information. 

Also, provide us with the updated complete API logs (request and response with request-id and request header) generated at your end to assist you better.

Since you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the .Net guide to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02rzM0M:ref"

Thanks,
 

Google Ads API Team

[Mads Grout]

This is exactly the generic answer i sadly wasn't looking for

Assuming these are the Quotas the UploadUserDataAsync is a mutate request if i am not mistaken? Unless this also is limited like the 1 QPS?..

https://developers.google.com/google-ads/api/docs/best-practices/quotas

Everything is working just fine using V14. We only bumped the Client library. So something underlying must have changed...

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to us.

As requested earlier, in order to debug the issue, provide us with the updated complete API logs (request and response with request-id and request header) generated at your end to assist you better.

Since you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the .Net guide to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email