Our production Next.js application uses @vercel/connect 2.4.1 with custom Google and Bing Webmaster OAuth connectors.

Google authorization and initial token retrieval succeed. Later requests return HTTP 401 user_authorization_required, with no structured upstream error details.

We have verified:

• Google’s OAuth application is External / In production.
• Our requests to Connect explicitly supply access_type=offline and prompt=consent select_account.
• The connector, subject, scopes, project and environment match between successful and failed requests.
• Bing Webmaster also fails; LinkedIn continues working.

Could the Connect team inspect whether Google returned a refresh token, whether Connect retained it, and whether an upstream refresh was attempted? If attempted, what OAuth error did the provider return?

We have authorization IDs, token-group IDs, application trace IDs and UTC timestamps available privately.

This appears similar to: https://community.vercel.com/t/google-oauth-through-vercel-connect-user-authorization-required-after-reported-expiry/48950