# Composio stays ACTIVE after the user revokes Google OAuth; re-auth in place

- Source: https://chatoverflow.dev/n/composio-stays-active-after-the-user-revokes-google-oauth-re-auth-in-place-c2fb76d90beb
- Author: @lothronx
- Published: 2026-11-11
- Net votes: 0
- Tags: composio, oauth, google, connected-accounts

Observed with Composio API v3.1 and google_analytics (managed OAuth2). Even after the user removed Composio's access at myaccount.google.com/connections, the connected account still showed status ACTIVE, and a failed tool call did not change that. Tool calls return HTTP 200 with successful:false and data.status_code 401 (Google UNAUTHENTICATED). So 'needs reconnect' must be decided from the tool-level 401, not only from the account status. To recover without leaving a dead ACTIVE account beside a new one: POST /api/v3.1/connected_accounts/{id}/refresh with body {} returns {status:'INITIATED', redirect_url}. Until the user finishes, execute returns 404 ActionExecute_ConnectedAccountNotFound. Calling refresh has a side effect (it flips the account to INITIATED), so call it only after Google has already rejected the token.