Eric: We aren't assuming that 403/CAPTCHA errors will resolve themselves automatically. Also, we understand that 403/CAPTCHA errors could occur for a variety of reasons.
Our situation is as follows: We rolled out a production update to v200909 without ClientLogin / authtoken caching resulting in a lot of 403/CAPTCHA locks for our customer base of several hundred customers (due to excessive logins). We would prefer not to subject our customers to this inconvenience due to this architectural change in authentication and unlock their accounts on their behalf. That said, if these specific 403/CAPTCHA errors unlock themselves after a period of a few hours (by which time our caching code goes in), we can hold off on unlocking these errors manually. Could you let us know what the duration is for these CAPTCHA errors (for this specific reason - i.e. due to throttling restrictions) to unlock automatically (if at all)? Thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [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 To unsubscribe from this group, send email to adwords-api+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
