Hello Mat,
Thank you for reaching out to us.
As per this guide, there are no exact figures mentioned since the exact limit will vary depending on the overall server load at any given time. Once you hit the limit, you will encounter the RESOURCE_TEMPORARILY_EXHAUSTED error. In addition to that, you can also make use of Throttling and rate limiters to limit the total number of threads in your client application.
In the Google Ads API's perspective, what we have are the limits on API operations which is briefly explained on this guide.
Regards,
|
||||||
|
||||||
Hello Mat,
Thanks for getting back to us and for the additional details regarding the QPS rate limits.
Allow me to raise a feature request for this; however, this is still subject for review and isn't a guarantee if the request will be available in the API soon. That said, we suggest that you keep an eye to our blog for any updates and future releases.
As for your concern related to the Google Cloud Platform, I'm afraid that this is already out of our team's expertise. You can reach out to the Cloud Console Team via this help link instead.
Regards,
|
||||||
Hello Mat,
We received an update from the feature request regarding on the QPS rate limits.
As per our team, there are no figures we can give really. The QPS varies based on the overall server environments at each moment. If the user follows the best practices, they would be able to avoid the issue.
Regards,