RateExceededError keep

[uvsuperDev]

Hi Guys

In the last 2-3 days we have started getting this error:

RateExceededError <rateName=BillingPerDay, rateKey=level1_plan, rateScope=DEVELOPER, retryAfterSeconds=86400>

The thing is that even after 24 hours we keep getting this error after 15-20 calls to the API (and not 10,000).

How can that be solved?

Thanks!

[Michael Cloonan (AdWords API Team)]

Hello,

This is a rate limiting error, not an error related to your daily operations. Please read more about Rate Limits on our developers site.

It is very important that, as soon as you receive an error like this, you stop making requests and wait the prescribed amount of time. If you continue to make requests before that wait time is expired, then the wait time will be extended up to a full day.

The linked guide has ideas and strategies about how to cope with rate limits.

Regards,

Mike, AdWords API Team

[Justin Coon]

We have been dealing with the exact same thing. But this seems really silly that we stop making requests for 24hrs. Basically that requires to stop our software completely...which effects our customers. So every time we make a subsequent request (after the initial error) the clock starts over??! We will never get back to ground zero

[Michael Cloonan (AdWords API Team)]

Hello Justin,

If you adhere to the timeouts specified in the rate limit errors, you will never be locked out for an entire day. Rate limits apply to all accounts, and they're enforced to make sure that one user cannot prevent the ability of another to use the API. You must honor the returned wait times specified by rate limits in order to make sure that your software does not get this last-resort 24 hour penalty. This penalty generally isn't issued the very first time you try to make a request that is rejected due to rate limit issues; you need to keep ignoring the errors and trying again before the specified time in order to get locked out for so long.

Once you implement wait and retry logic, you should never get locked out for more than a few minutes, or probably even less than that.

Regards,

Mike, AdWords API Team

[Justin Coon]

Does the clock reset the 24 hrs every time a subsequent request is made (the request obviously still fails)?

[Michael Cloonan (AdWords API Team)]

Hello,

If you continue to make requests when rate limited, then the clock will reset each time, yes. It really is in your best interest to wait the amount of time the error indicates, every time, even if that time is an entire day.

Regards,

Mike, AdWords API Team

[Justin Coon]

Is it possible to get a grace extension for a day or so to remove the 24hr ban while I put more logic to handle the more transient rate limit errors and deploy that code? I've already changed through our config file to download reports on a less often interval so that should help alot, but I need more logic to better handle the 'warning' 30 second timeouts

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "AdWords API Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adwords-api/FRfQrbD2csE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adwords-api...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/cab0cf01-0d47-44a0-ba2d-b8e96a91fb46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kristopher Windsor]

I am also seeing this error. Our application has been running for months without major changes, and we just noticed many rate exceeded errors starting yesterday. We have a token bucket implementation, exponential back-off strategy, everything that was recommended. I think something has changed on Google's end.

We are also seeing many unexpected internal API errors (more than usual) -- these errors are persistent enough that our scripts give up retrying. (This is not usual.)

 [RateExceededError <rateName=Requests, rateKey=shasta, rateScope=ACCOUNT, retryAfterSeconds=30>]"

[Michael Cloonan (AdWords API Team)]

Hello Kristopher,

Based on the number of reports, and your description, I am starting to suspect like you that something may be wrong on our end. Can you please reply to me privately and include an example SOAP request/response where you're getting the rate limiting error at a time where you normally wouldn't have? I will pass it along to the engineers so that they can look at a specific example to see what might be going wrong.

Regards,

Mike, AdWords API Team

[uvsuperDev]

Hello Michael,

We are well aware to the rate limits and we have implemented all your best practices (using mutateJobService, waits etc.). As I have written on my original post we keep getting this after the 24 hours penalty after making another 15-20 calls within a hour (that isn't too much, right?).

I am really suspecting that something has gone wrong on your end since our tool was working perfectly for months. 

Any other solutions? Is there a way to find our the exact reason we get this error?

Thanks!

[Justin Coon]

Let me also add that our analytics tool has been working without this issue for at least 6 months as well. No changes on our end, but this just started happening within the last few days. We download reports, and make a few read-only calls related to account structure, campaigns, and ads.

Thanks

Justin

[Michael Cloonan (AdWords API Team)]

Thanks everyone for the reports. I've filed a bug with our engineering team to look into this issue, and I will keep this thread updated as I hear back.

Regards,

Mike, AdWords API Team

[Michael Cloonan (AdWords API Team)]

Hello,

Everyone who is experiencing this issues, please reply to me privately with your developer token and CID so that we can narrow down and take a closer look at specifically known affected accounts. The engineering team is actively looking into this issue.

Regards,

Mike, AdWords API Team

[Michael Cloonan (AdWords API Team)]

Hello again,

One other followup question. For users this is affecting, is it specifically only affecting reporting, or are you also seeing this behavior with other services?

Regards,

Mike, AdWords API Team

[Justin Coon]

We mostly use reporting, but we do use other read-only services for example

Google.Api.Ads.AdWords.v201502.CampaignService.get

[Yuval Haimov]

We use the CampaignCriterionService and CampaignService as well as the MutateJobService. all under v201506.

No reporting at all.

[Eric Berry]

I'm seeing this when using the TargetingIdeaService

[Kristopher Windsor]

We mainly do these things:

• Report queries
  
  ReportDownloadError.ERROR_GETTING_RESPONSE_FROM_BACKEND
• Entity / read-only queries to get campaigns, ads, etc
  
  InternalApiError.UNEXPECTED_INTERNAL_API_ERROR
• Submit CPC bids in batch
  --> This seems to work OK
  

Thanks,

[Michael Cloonan (AdWords API Team)]

Hello,

We have just pushed a change to production that should hopefully resolve this issue. If anyone can confirm that the problem is fixed, please let me know.

Regards,

Mike, AdWords API Team

[Mark Rogoyski]

Hi Mike,

Thank you for the update. We are currently not seeing any of the 500s with the InternalApiError.UNEXPECTED_INTERNAL_API_ERROR that we were seeing before. I will keep monitoring it and update if something changes.

Thanks.

Mark

[Justin Coon]

We are again seeing this issue. It appears to be with https://adwords.google.com/api/adwords/cm/v201502/AdGroupService AdGroupService

Is there a fix coming soon?

[Justin Coon]

Also seeing it with the https://adwords.google.com/api/adwords/cm/v201502/CampaignService CampaignService

However we dont see the issue with the reports portion of API

[Michael Cloonan (AdWords API Team)]

Hello,

Thank you for the report that this is occurring. We've also heard this from a few other sources, and I've already contacted our engineering team to take a look at what's going on.

Regards,

Mike, AdWords API Team