Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello Charles, Thanks so much for your valuable feedback! I'll update the doc so people don't get misunderstood about the *retryAfterSeconds* value again. Best, Thanet, AdWords API Team On Wednesday, October 5, 2016 at 3:56:21 PM UTC+9, Charles Michael wrote: > > Thanks for the update, I'm curr

Re: RetryAfterSeconds=30, Still Not Working After 30.

Thanks for the update, I'm currently waiting between 40-50 seconds which is pretty much as you suggested, a multiplier between 1-2X of 30 seconds. I looked into BatchJobService, and while it seems promising being able to retry requests automatically, it doesn't seem to have support for Targeti

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hi Charles, Thanks for more insight. I've discussed with engineering team and unfortunately, due to technical issues, we can't provide the exact waiting time via *retryAfterSeconds*. So, we suggest that you treat the *retryAfterSeconds* as the lower bound of your waiting time, and apply a rando

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello, During peak hours, 100 seconds would be ideal. However, at 2am (EST) when the load is much less, the wait time can be as little as 10 seconds. Having to wait 90 seconds extra per request is quite an excessive amount of time to wait between requests when 10 is sufficient in offhours. I'm

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello Charles, Could you please clarify why 100 seconds are too excessive? I would like to use this information for discussion with engineering team as well. Currently, the exponential backoff policy is encouraged to be used in many places of AdWords API, so 100 seconds is what we can expect in

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hi, I remember when you first suggested the pseudocode for this but I never implemented it because I couldn't come up with a way to come back down in value over time. As I recall, you would double the wait time on every Retry request until the requests go through. If I ran this during peak hour

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello Charles, Have you considered to use the exponential backoff policy as I mentioned in the previous reply? The exponential backoff policy shouldn't be difficult to implement, as illustrated in the AddCompleteCampaignUsingBatchJob

Re: RetryAfterSeconds=30, Still Not Working After 30.

Sorry for bumping this again, but the issue has gotten progressively worse. Starting about an hour ago (noon EST), with wait times of 40 seconds, I'm failing with the same retry after 30 second errors. Was there any feedback from the engineering team as its very difficult to code something when

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello Charles, Thanks for your valuable feedback. I'll pass this to engineering team as well. I'll keep this post updated when I have any more news. Cheers, Thanet, AdWords API Team On Saturday, September 24, 2016 at 3:40:19 AM UTC+9, Charles Michael wrote: > > The only issue with this strategy

Re: RetryAfterSeconds=30, Still Not Working After 30.

The only issue with this strategy though is you could potentially be pausing for excessively long periods of time. During peak hours I would be pausing upwards of 60 seconds, but there isn't an efficient way for the pause time to come back down, especially when its no longer peak hours. If I m

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello Charles, I'm still waiting for the final answer of this. A solution for now is to use exponential backoff policy, for example, if you first pause 5 seconds before the first retry, you could pause 10 seconds after the second and 20 seconds after the third retry, instead of following the *r

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hi, was there any update to this? Since originally posting this, I've narrowed the issue to only occurring between 12pm - 5pm EST, outside of this range there are no issues with taking more than 30 seconds between requests. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello, Could you please send your SOAP logs by *Reply privately to author* too? Thanks in advance. Best, Thanet, AdWords API Team On Sunday, September 18, 2016 at 7:39:13 AM UTC+9, vj wrote: > > I am also getting same Error while using this service...I am getting this > error even after no acti

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello Charles, I've reported this to engineering. I'll get back to you once I have more updates. Cheers, Thanet, AdWords API Team On Saturday, September 17, 2016 at 4:24:04 AM UTC+9, Charles Michael wrote: > > I've sent you the logs, thanks for your help. > > On Friday, September 16, 2016 at 1

Re: RetryAfterSeconds=30, Still Not Working After 30.

I am also getting same Error while using this service...I am getting this error even after no activity since last 24 hours on api request... On Thursday, September 8, 2016 at 10:01:10 PM UTC+5:30, Charles Michael wrote: > > Hello, I have a standard account and I'm currently running a lot of > T

Re: RetryAfterSeconds=30, Still Not Working After 30.

I've sent you the logs, thanks for your help. On Friday, September 16, 2016 at 1:27:28 AM UTC-4, Thanet Knack Praneenararat (AdWords API Team) wrote: > > Hello Charles, > > Just the latest request that you sent and got the rate exceeded error > would be fine. > You don't need to send all of the

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello Charles, Just the latest request that you sent and got the rate exceeded error would be fine. You don't need to send all of them. Thanks! Best, Thanet, AdWords API Team On Friday, September 16, 2016 at 5:15:01 AM UTC+9, Charles Michael wrote: > > Unfortunately it's over 5 gigs large as I

Re: RetryAfterSeconds=30, Still Not Working After 30.

Unfortunately it's over 5 gigs large as I never flushed it since the beginning (over a year worth of logs). I just flushed it and will re-run. Do you want the entire log or specific entries? If the latter, what criteria would like me to include? On Thursday, September 15, 2016 at 12:10:13 AM

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hi Charles, Could you please provide the SOAP log by *Reply privately to author*? Best, Thanet, AdWords API Team On Thursday, September 15, 2016 at 7:30:14 AM UTC+9, Charles Michael wrote: > > Hi again, for the most part, it seems that its rather stable now, but > between 12pm - 5pm EST on most

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hi again, for the most part, it seems that its rather stable now, but between 12pm - 5pm EST on most business days (not weekends), I was hitting the retry after 30 seconds where it was taking more than 30 seconds to reset. It's a little frustrating, but for 19 hours per day it works without iss

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hi, my scripts ran through the weekend with just a couple failures (it worked after RetryAfterSeconds=30), but since this is the first business day back, let's see if it fails during business hours. If it consistently fails after 30 seconds, I'll send you a private message with the account info

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hello Charles, I'm investigating this with engineering, so could you please send us your client customer ID via *Reply privately to author*? Also, do you still face this situation consistently for everyday's peak time? Thanks. Thanet, AdWords API Team On Saturday, September 10, 2016 at 6:09:17

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hi, I am the only developer with access to the API, so scenario #2 is applicable. My main issue is that the retry after 30 seconds isn't actually valid, it seems to be much longer and I can't really code a throttle if the time being reported is inaccurate. The advice from the pages linked basic

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hi Charles, I can recommend a couple things: 1) Since the rateScope is ACCOUNT, could you confirm if your AdWords account is being accessed via another developer token or OAuth credentials (could be through another MCC that the AdWords account is linked to)? 2) If #1 is false, i.e. you are the

Re: RetryAfterSeconds=30, Still Not Working After 30.

[RateExceededError ] I have read the rate limits guide, but the issue is that the API is not lifting the block after 30 seconds despite the API telling me to retry after 30 seconds. I also already have a standard account. PS: This issue seems to be particular hitting me during peak hours, betw

Re: RetryAfterSeconds=30, Still Not Working After 30.

Hi Charles, When you receive the RATE_EXCEEDED error, what do you see as the *rateName *in the err

RetryAfterSeconds=30, Still Not Working After 30.

Hello, I have a standard account and I'm currently running a lot of TargetingIdeaSelector lookups with v201607 (just upgraded from v201601) and I'm hitting the RATE_EXCEEDED (Account) error where the RetryAfterSeconds is 30. I've waited several minutes and relaunched my script to keep hitting t

Re: RetryAfterSeconds=30, Still Not Working After 30.

As a side note, its been over 15 minutes and I'm getting the same RATE_EXCEEDED with 30 second retry notice on the first request I send. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com