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 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 UTC-4, Thanet Knack > Praneenararat (AdWords API Team) wrote: >> >> 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 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 >>> issue at 30 second sleepers. I was assuming that if I space my requests >>> every 30 seconds I wouldn't hit the rateexceeded issue, but it seems >>> apparent that its actually longer than 30 seconds during business hours >>> which is when I assume the API is getting hit the most frequently. >>> >>> >>> On Sunday, September 11, 2016 at 10:32:56 PM UTC-4, Thanet Knack >>> Praneenararat (AdWords API Team) wrote: >>>> >>>> Hello Charles, >>>> >>>> I'm investigating this with engineering, so could you please send us >>>> your client customer ID via *Reply privately to author*? >>>> And if you happen to have SOAP logs containing *retryAfterSeconds*, >>>> could you please send that along to me too? >>>> 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 AM UTC+9, Charles Michael >>>> wrote: >>>>> >>>>> 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 >>>>> basically says to wait 30 seconds, but when I do, I get the same error >>>>> right away. I don't want to trigger a longer ban, so I've instituted a >>>>> halt >>>>> on my script when there's a rate exceeded error. Based on the load volume >>>>> you mentioned, that would make sense why I can run my script at night >>>>> without problems, but I should still be able to access it during peak >>>>> hours >>>>> as well. Since the weekend is coming up, I'll give it a shot with a >>>>> longer >>>>> sleeper in place, but it would be great to actually get an accurate >>>>> figure >>>>> on how long to throttle the script by as the suggestion by google's api >>>>> of >>>>> waiting 30 seconds isn't accurate. >>>>> >>>>> >>>>> >>>>> >>>>> On Friday, September 9, 2016 at 4:30:13 PM UTC-4, Vishal Vinayak >>>>> (Adwords API Team) wrote: >>>>>> >>>>>> 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 only entity accessing your >>>>>> AdWords account in your application, I would recommend slowing down the >>>>>> number of requests that you send per second by following some of the >>>>>> strategies mentioned on this page >>>>>> <https://developers.google.com/adwords/api/docs/guides/rate-limits#take_control> >>>>>> . >>>>>> >>>>>> Also, the number of queries that you can send to the API per second >>>>>> varies dynamically based on the current load on the servers. Hence you >>>>>> might see this error only during peak hours and the application might >>>>>> seem >>>>>> to work normally otherwise. >>>>>> >>>>>> Regards, >>>>>> Vishal, AdWords API Team >>>>>> >>>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/dcf069e1-8f38-491d-bdfd-361c92fd4857%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
