Hi,
This seems like this issue is related an internal error with refreshing the
access token. In general, if access tokens cannot be refreshed, you should
try again after 30 seconds. If this does not work, you should try to do the
OAuth2 flow again and get a hold of another access token.
In
I'm running into the same problem with the server side. Our platform is
essentially a server that runs infinitely to download-process-update ad
groups/campigns,etc..the same code runs on multiple server instances on
multiple machines. After 1 day or so, some servers start getting the below
stack trace for the below error
at
Google.Api.Ads.Common.Lib.OAuth2ProviderForApplications.RefreshAccessTokenInOfflineMode()
at
Google.Api.Ads.Common.Lib.OAuth2ProviderForApplications.RefreshAccessToken()
at
Google.Api.Ads.Common.Lib.OAuth2ProviderBase.RefreshAccessTokenIfExpiring()
Hi,
Can someone from the AdWords team please help with resolving this issue. It
has been happening every day for the past 10 days.
ERROR 2014-01-21 03:30:33 21896 [Vulcan::Google]:
msg:#AdsCommon::Errors::AuthError: OAuth2 token refresh failed
Hi,
We are seeing this same error for the past few days using the Ruby client.
We make two scheduled attempts to download data at 3:30 AM and 5:30 AM,
they both fail with the same error. Manual re-try at 7AM usually succeeds.
ERROR 2014-01-21 03:30:33 21896 [Vulcan::Google]:
Hi Anash,
Thanks for your response and the suggestion. We are already reusing
OAuthProvider instances do reduce refresh frequency. We had experienced
rate limit errors from the OAuth2 servers before (see http://goo.gl/wdDEKU)
and the error page was different - is it possible to receive
Hi All,
We've noticed a weird authentication error that was occurring on one of our
application servers over the weekend. All of our *MutateJobService.mutate* API
calls were failing with the error below across multiple accounts. The weird
thing is all other API calls were unaffected and the
Hi Akil,
My initial guess is that the page is a rate limit error from the OAuth2
servers (too many instances trying to refresh access token simultaneously).
It's a matter of chance that a particular server failed, and the error
would go away if the code were retried after a minute or so.
You
