Hello, Unfortunately, my team doesn't have any insight into why a refresh token may have been revoked. If it stopped working unexpectedly, it's most likely because the user either revoked it or generated a new one for some other purpose which brought them over the limit of maximum simultaneous refresh tokens.
If you're using a flow where users have to sign in to access their account through your service (which is what it sounds like, based on your description), you should just build in a way for them to re-authenticate if things go wrong. Regards, Mike, Google Ads API Team ref:_00D1U1174p._5001UZXKqw:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads 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 --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/2798L000000000000000000000000000000000000000000000Q8UAR600TNMpXcW1R22__QWTSxZx8A%40sfdc.net.
