https://linen.dev logo
OAuth Connection Status Stuck at INITIATED for "Br...
# 🖥│support-forum
s
I'm integrating your platform into my application and my main goal is to onboard MCP tools onto my platform so what i am doing is build the MCP gateway through composio instead of intrgrating each tool at a time. I have ran into a persistent issue where the connection status for a user-provided OAuth credential for Gmail remains stuck at INITIATED and never transitions to ACTIVE. I have confirmed the following: Application Architecture: I have a FastAPI backend that uses the composio-python-sdk to initiate the connection and poll for status, and a Streamlit frontend. Auth Config: I am using a "Bring Your Own Credentials" Auth Config. Auth Config ID: ac_wZu6_Voj70RM A sample Connected Account ID that is stuck is: ca_j2OhOsU7Avcq Google Cloud Configuration: My OAuth Client ID in Google Cloud has been meticulously configured with: The correct Authorized Redirect URI: https://backend.composio.dev/api/v1/auth-apps/add The correct Authorized JavaScript origin: https://backend.composio.dev My app is in "Testing" mode, and I have added my test email as an authorized "Test user". User Flow: I successfully complete the Google authorization flow and receive the "You allowed Composio access..." security email from Google every time. Application Logic: My backend successfully polls the connected_accounts.retrieve() endpoint. The raw response from your API consistently shows status='INITIATED' even minutes after successful user authorization. I have already performed a full "clean slate" reset (revoking app access in Google, clearing browser cache, deleting old connections) to no avail. The logs from my application confirm that my code is correctly calling your SDK and that your API is consistently returning the INITIATED status. Could you please investigate on your end why the webhook or callback from Google might not be successfully updating the status of my connected accounts for this specific Auth Config?
c
Hi Soumya, Just to clarify— You are completing the Auth Flow and are still stuck at INITIATED?
s
Yes, that is exactly correct. Here's the flow: I initiate the connection from my app and get the redirect_url. I go to the URL, complete the entire Google Auth flow, and click "Allow". I immediately receive the "You allowed Composio access to some of your Google Account data" security email from Google, confirming I successfully authorized. However, when my backend polls the connected_accounts.retrieve() endpoint for that connection ID, the status remains INITIATED indefinitely and never becomes ACTIVE. The specific Auth Config ID we are using is ac_wZu6_Voj70RM, and a sample Connected Account ID that is stuck at INITIATED is ca_a4Jg5sNSxcEs. It seems the final callback from Google isn't updating the status in your system for this specific "Bring Your Own Credentials" setup.
c
Could you share a screen recording of the Auth flow?
s
First of, is that possible that i want to implement a MCP gateway through composio instead of having to integrate each tool one by one?
c
You can use [mcp.composio.dev](http://mcp.composio.dev) to directly connect an Account and create MCP servers.
2 Views