RATE_EXCEEDED without trigger on fetching reports

[Jason W]

When pulling reports for a particular account, we're encountering RATE_EXCEEDED errors without any additional information about the trigger. These types of requests generally succeed for other clients, and we still get this error if we add delay between requests for the account in question, so we're unsure about whether or not we're hitting a QPS limit.

Example request:

Report request to: 'https://adwords.google.com/api/adwords/reportdownload/v201802'

HTTP headers: [Content-Type: application/x-www-form-urlencoded, Authorization: Bearer [REDACTED], User-Agent: (AwApi-Ruby/1.1.1, Common-Ruby/1.0.1, GoogleAdsSavon/1.0.3, ruby/2.1.5, HTTPI/2.4.3, httpclient), clientCustomerId: [REDACTED], developerToken: [REDACTED]]

__rdxml=%3CreportDefinition%3E%3Cselector%3E%3Cfields%3EDate%3C%2Ffields%3E%3Cfields%3EAveragePosition%3C%2Ffields%3E%3Cfields%3EClicks%3C%2Ffields%3E%3Cfields%3EImpressions%3C%2Ffields%3E%3Cfields%3ECost%3C%2Ffields%3E%3Cfields%3EConversions%3C%2Ffields%3E%3Cfields%3ECampaignId%3C%2Ffields%3E%3Cfields%3EViewThroughConversions%3C%2Ffields%3E%3Cfields%3EConversionValue%3C%2Ffields%3E%3Cfields%3ENumOfflineImpressions%3C%2Ffields%3E%3Cfields%3ENumOfflineInteractions%3C%2Ffields%3E%3Cpredicates%3E%3Cfield%3ECampaignId%3C%2Ffield%3E%3Coperator%3EEQUALS%3C%2Foperator%3E%3Cvalues%3E1047146106%3C%2Fvalues%3E%3C%2Fpredicates%3E%3CdateRange%3E%3Cmin%3E20180416%3C%2Fmin%3E%3Cmax%3E20180422%3C%2Fmax%3E%3C%2FdateRange%3E%3C%2Fselector%3E%3CreportName%3ECAMPAIGN_PERFORMANCE_REPORT%3C%2FreportName%3E%3CreportType%3ECAMPAIGN_PERFORMANCE_REPORT%3C%2FreportType%3E%3CdateRangeType%3ECUSTOM_DATE%3C%2FdateRangeType%3E%3CdownloadFormat%3ECSV%3C%2FdownloadFormat%3E%3C%2FreportDefinition%3E

HTTPI /peer POST request to adwords.google.com (httpclient)

HTTP headers: [Content-Type: text/xml, Content-Encoding: gzip, Date: Mon, 07 May 2018 22:21:31 GMT, Expires: Mon, 07 May 2018 22:21:31 GMT, Cache-Control: private, max-age=0, X-Content-Type-Options: nosniff, X-Frame-Options: SAMEORIGIN, X-XSS-Protection: 1; mode=block, Server: GSE, Alt-Svc: hq=":443"; ma=2592000; quic=51303433; quic=51303432; quic=51303431; quic=51303339; quic=51303335,quic=":443"; ma=2592000; v="43,42,41,39,35", Transfer-Encoding: chunked]

[ERROR] HTTP code: 400, error type: 'RateExceededError.RATE_EXCEEDED', trigger: '', field path: ''

Any information about why we might be seeing the rate limit error for this account would be greatly appreciated. I'm happy to provide additional information or logs as well.

[Dannison Yao (AdWords API Team)]

Hi Jason,

The reason you are getting RATE_EXCEEDED is because you might have exceeded the operational limit based on your access level or you had a system limit which means that your application makes a high number of requests per second on a single AdWords account. Please refer to this guide for further details. It is also unusual that there is no trigger shown in your logs, because usually there is a reason provided for that error. Can you provide me the complete error logs or the SOAP request and response logs and your clientCustomerId via Reply privately to author so I can further investigate on this?

Regards,

Dannison

AdWords API Team