Hey guys - I've got a pattern in place for all of my api calls that wraps the api call so that if it throws an exception, the api call will be retried several times before giving up. Once the retry limit is reached, we then clear the client credentials from the cache. Upon the next api call, we get fresh credentials, cache them, and process along. This has worked great for several years. Today the follow-on login requests appeared almost uniformly to result in a "CaptchaRequired" exception. Can you shed some light on what may have changed to cause so many Captchas now?
Thanks - mm -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
