CRITICAL: BYOC Connection is ACTIVE but gets 401 Unauthorized from Google
Hi Team,
I've discovered a critical issue with the "Bring Your Own Credentials" flow for Gmail. My connection status successfully becomes ACTIVE, but every subsequent tool execution fails.
My application logs show that when I call tools.execute, your API returns a 200 OK, but the content of the response is a 401 Unauthorized error from Google. This proves the token your backend is using is invalid.
Auth Config ID (BYOC, Failing): ac_wZu6_Voj70RM
Sample Connection ID: ca_ldyGbmW5UF_-
Log from my service:
DICTIONARY BEING RETURNED FROM SERVICE for tool 'gmail_get_profile': {'error': '401 Client Error: Unauthorized for url:
https://www.googleapis.com/gmail/v1/users/me/profile', 'successful': False, ...}
This indicates a token management issue on your platform for BYOC setups. I have switched to a Composio-managed config to unblock myself, but this appears to be a major bug.