Hi, starting this morning, we're experiencing similar issues. The throughput rates we've got from the TrafficEstimatorService were pretty stable over the past months but today, we get a lot of RateExceededErrors (the same as illustrated by Alexander). Waiting for 30 seconds sometimes helps and sometimes doesn't. We've already noticed a slight increase in RateExceededErrors over the past days and they were always recoverable. Now, we wonder if the rate limit for the TrafficEstimatorService has been changed or if this is just a temporary behavior.
Best regards, Stefan Am Montag, 28. September 2015 15:46:24 UTC+2 schrieb Alexander Nitschke: > > Hi, > > we are using the TrafficEstimatorService in our UI to give advice for > expected clicks and cost during campaign creation (similar to the Adwords > UI). This used to work fine, but today this feature is practically broken. > The reason is a very often occurring RateExceededError (which we practially > never saw during the history of this feature use). The detailed error > message is: > > [RateExceededError <rateName=RATE_LIMIT, rateKey=null, rateScope=ACCOUNT, > retryAfterSeconds=30>] > > This is rather nondescript as far as error details go... but at least it > actually suggests that the scope of this error is ACCOUNT, right? This > seems to be just not true, as this error also can occur in the first ever > usage of the TrafficEstimatorService for an account. In my tries it seems > more like the Rate is affected over all accounts of an MCC (or maybe even > over the developer token?). First call after some pause works, but another > call on a different account soon after might not work. This behaviour makes > this error especially painful as you can imagine. > > I know that the TrafficEstimatorService might be a sensible service to > use, but our usage is just as intended and historically does not produce an > excessive number of calls over any span of time, quite on the contrary. > > I'm still hoping the TrafficEstimatorService is just having a bad day and > the issue gets resolved soon?!? > > Note: A few weeks ago there was another bad TrafficEstimator day with the > estimates being all over the place (like submissing fewer keywords, and > getting more instead of fewer clicks etc). This could be reproduced in the > Adwords UI actually, so it wasn't an API matter and thus not relevant for > this forum; luckily the next day everything was back to normal. But this > time it really looks like an API problem, so now here is my call for help. > > Best regards, > Alexander > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@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 the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@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/2d09ef35-5040-4f4c-8836-c23fa80be35c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
