Thanks for the explanation - the error makes sense now. Funniest thing happened this morning, for one of the previous offending accounts the software got an auth token without problems, but a later call to the (legacy) AccountService produced error 86, "The specified account has been blocked due to excessive failed logins." The error came without a request id. And I can't reproduce that one either, apparently those blocked accounts are also unlocked after five minutes. Can you confirm that?
Anyway, I'll rewrite the software to cache the authtokens. One more question, how can I enforce this situation on a test account? Thanks, - Zweitze. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Have you migrated to v200909 yet? The v13 sunset is on April 22, 2010. Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
