Academy
7. Troubleshooting and Disconnecting Services
Diagnose broken connections caused by expired or revoked authorizations, re-authorize or recreate them, and perform a clean disconnection on both the OUPI and service sides.
When an MCP connection stops working, the root cause is almost always an expired or revoked authorization on the external service's side. OAuth tokens have lifetimes; if the service rotates or invalidates yours — or if you changed your password, revoked access from the service's connected-apps page, or the service updated its required scopes — the connection goes stale. OUPI cannot call tools through a dead authorization, so every tool exposed by that connection silently fails. The first diagnostic step is always the execution log: open it to inspect recent tool calls and check their outcomes. A string of failures on one connection, while others succeed, confirms the authorization is the problem, not the platform.
To fix a broken connection, navigate to your Connections list and open the affected one. You have two paths:
- Re-authorize — If the service supports token refresh, trigger re-authorization from the connection detail. You will go through the OAuth flow again, grant the required scopes, and the existing connection (with all its tool mappings) stays intact.
- Recreate — If re-authorization is not offered or the service changed its permission model, delete the old connection and create a new one from the server catalog. You will authenticate fresh and grant the updated scopes.
Because connections work platform-wide (ChatPro, Studio, workflows, RAG imports, Deep Research), restoring one connection restores tool access everywhere simultaneously.
Before re-authorizing, open the connection's tool list to verify the tools the AI sees. If the service added or removed capabilities, you'll spot the mismatch immediately — and know whether a simple re-auth suffices or a full reconnection with new scopes is needed.
A clean disconnection requires action on both sides. In OUPI, delete the connection from the MCP Hub — this removes it platform-wide, so no AI feature (ChatPro badges, Studio agents, workflow steps, Deep Research) can invoke its tools anymore. Then go to the external service's own settings (usually under "Connected Apps" or "Authorized Applications") and revoke the OAuth grant. Skipping the service-side revocation leaves a dangling authorization that could theoretically be reused. Doing both ensures a complete, auditable cleanup.
After deleting a connection, check the execution log one last time. Any tool calls that were in-flight will show a final outcome there, confirming the disconnection took effect and no residual calls slipped through.
Open your MCP Hub → Connections. Pick a connection and open it to inspect its tool list. Then navigate to the Execution Log and filter by that connection to review recent call outcomes. Identify any failures and note whether they point to an authorization issue.
Broken MCP connections almost always trace back to expired or revoked OAuth tokens. Diagnose by checking the execution log for failure patterns, then re-authorize or recreate the connection. For a clean disconnect, delete the connection in the MCP Hub (removes it platform-wide) and revoke the grant on the service side. Always verify via the execution log that no residual calls remain.