Hi all, As recommended in articles like http://adwordsapi.blogspot.com/2010/07/discover-v2009-working-with-authtokens.html we store authentication tokens externally instead of re-requesting them over and over again. In our implementation they are stored in a database, with a datetime stamp so we know when to refresh them. Today, we get many errors on cached authentication tokens. I mean dozens fail. (Tomorrow I may have a better number). All tokens were less than a week old, because we refresh the token after seven days.
This has never happened before. So.... why? Note: I know the solution would be to stop caching auth tokens, but Google convinced me to not go that way. So the software should detect this error and re-request an auth token. Unfortunately we also use the Adwords Library for .NET which appears totally unsuited for this situation. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
