Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 22, 10:45 UTC
docs: clean up troubleshooting pages
- dashboard: remove images, simplify to text-only - mcp: update images, revert link to Single Toolkit MCP - sdks: remove images, simplify debug log instructions - tools: fix JSON diff markers, clarify log_id sources, update image - triggers: clarify dashboard location, update image Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 4, 2026 at 15:18 UTC
2e451286ccdd8357394584d140a6e3184456b795
14 files changed
+10
-46
docs/content/docs/troubleshooting/dashboard.mdx
+5
-25
@@ -8,31 +8,11 @@ description: Troubleshooting dashboard issues
8
When reporting dashboard issues to support, provide:
9
10
- **Screenshot or recording**: Visual evidence of the issue
11
-- **Error details**: Complete error message shown in the UI. For example:
12
-
13
- <img
14
- src="/images/troubleshooting/troubleshooting-dashboard-ui-error.png"
15
- alt="Example dashboard UI error: A project with this name already exists"
16
- style={{ maxWidth: '640px', width: '100%', marginTop: '12px', marginLeft: '0.5rem', borderRadius: '8px', display: 'block' }}
17
- />
18
-
19
-- **Network logs**: Check browser DevTools for failing API calls and share:
20
- - Error message
21
- - Request ID (`x-request-id` header)
22
-
23
- <img
24
- src="/images/troubleshooting/troubleshooting-dashboard-request-id.png"
25
- alt="Tool call error"
26
- style={{ maxWidth: '720px', width: '100%', marginTop: '12px', marginLeft: '0.5rem', borderRadius: '8px', display: 'block' }}
27
- />
28
-
29
- - Failed endpoint URL (`https://backend.composio.dev/api/v3/org/project/new`)
30
-
31
- <img
32
- src="/images/troubleshooting/troubleshooting-dashboard-rename-error.jpg"
33
- alt="Example network log and dashboard error for a failed tool call"
34
- style={{ maxWidth: '720px', width: '100%', marginTop: '12px', marginLeft: '0.5rem', borderRadius: '8px', display: 'block' }}
35
- />
11
+- **Error details**: Complete error message shown in the UI
12
+- **Network logs**: Check browser DevTools (Network tab) for failing API calls and share:
13
+ - Request ID (`x-request-id` response header)
14
+ - Failed endpoint URL
15
+ - Status code and error response
16
17
## Getting help
18
docs/content/docs/troubleshooting/mcp.mdx
+1
-1
@@ -13,7 +13,7 @@ This error occurs when MCP cannot find a valid connected account for authenticat
13
- Account status is `ACTIVE` (not deleted)
14
- Account belongs to the same auth config used to create the MCP server
15
16
-Learn more: [MCP Developer Guide](/docs/mcp-developers#client-applications-connect-to-the-server)
16
+Learn more: [Single Toolkit MCP](/docs/single-toolkit-mcp)
17
18
## Getting 404 errors
19
docs/content/docs/troubleshooting/sdks.mdx
+1
-17
@@ -22,23 +22,7 @@ COMPOSIO_LOG_LEVEL=debug
22
</Tab>
23
</Tabs>
24
25
-Once debug logging is enabled, you can find the `x-request-id` in your SDK logs:
26
-
27
-- **Python SDK example**
28
-
29
- <img
30
- src="/images/troubleshooting/troubleshooting-sdk-py-request-id.png"
31
- alt="Example of x-request-id highlighted in Python SDK debug logs"
32
- style={{ maxWidth: '720px', width: '100%', marginTop: '12px', marginLeft: '0.5rem', borderRadius: '8px', display: 'block' }}
33
- />
34
-
35
-- **TypeScript SDK example**
36
-
37
- <img
38
- src="/images/troubleshooting/troubleshooting-sdk-ts-request-id.png"
39
- alt="Example of x-request-id highlighted in TypeScript SDK debug logs"
40
- style={{ maxWidth: '720px', width: '100%', marginTop: '12px', marginLeft: '0.5rem', borderRadius: '8px', display: 'block' }}
41
- />
25
+Look for `x-request-id` in the debug output to share with support.
26
27
## Check SDK version
28
docs/content/docs/troubleshooting/tools.mdx
+2
-2
@@ -47,7 +47,7 @@ When reporting to support, provide:
47
```json
48
{
49
"data": {
50
- "message": "{\n \"error\": {\n \"code\": 404,\n \"message\": \"Requested entity was not found.\",\n \"errors\": [\n {\n \"message\": \"Requested entity was not found.\",\n \"domain\": \"global\",\n \"reason\": \"notFound\"\n }\n ],\n \"status\": \"NOT_FOUND\"\n+ }\n+}\n",
50
+ "message": "{\n \"error\": {\n \"code\": 404,\n \"message\": \"Requested entity was not found.\",\n \"errors\": [\n {\n \"message\": \"Requested entity was not found.\",\n \"domain\": \"global\",\n \"reason\": \"notFound\"\n }\n ],\n \"status\": \"NOT_FOUND\"\n }\n}\n",
51
"status_code": 404
52
},
53
"successful": false,
@@ -56,7 +56,7 @@ When reporting to support, provide:
56
}
57
```
58
59
-- **Log ID**: From the error response.
59
+- **Log ID**: From the error response (`log_id` field), or find it in the dashboard Logs page:
60
61
<img
62
src="/images/troubleshooting/troubleshooting-tool-log-id.png"
docs/content/docs/troubleshooting/triggers.mdx
+1
-1
@@ -23,7 +23,7 @@ Even if the action occurred (email received, Jira issue created, etc.), there ma
23
When reporting to support, provide:
24
25
- **Error message**: Complete error details
26
-- **Connected account and trigger IDs**: The connected account ID used for creating the trigger and the specific trigger ID that's failing
26
+- **Connected account and trigger IDs**: Find these in the dashboard under Active Triggers:
27
28
<img
29
src="/images/troubleshooting/troubleshooting-trigger-id.png"
docs/public/images/troubleshooting/troubleshooting-dashboard-rename-error.jpg
Binary files a/docs/public/images/troubleshooting/troubleshooting-dashboard-rename-error.jpg and /dev/null differ
docs/public/images/troubleshooting/troubleshooting-dashboard-request-id.png
Binary files a/docs/public/images/troubleshooting/troubleshooting-dashboard-request-id.png and /dev/null differ
docs/public/images/troubleshooting/troubleshooting-dashboard-ui-error.png
Binary files a/docs/public/images/troubleshooting/troubleshooting-dashboard-ui-error.png and /dev/null differ
docs/public/images/troubleshooting/troubleshooting-mcp-connected-account-id.png
Binary files a/docs/public/images/troubleshooting/troubleshooting-mcp-connected-account-id.png and b/docs/public/images/troubleshooting/troubleshooting-mcp-connected-account-id.png differ
docs/public/images/troubleshooting/troubleshooting-mcp-server-url.png
Binary files a/docs/public/images/troubleshooting/troubleshooting-mcp-server-url.png and b/docs/public/images/troubleshooting/troubleshooting-mcp-server-url.png differ
docs/public/images/troubleshooting/troubleshooting-sdk-py-request-id.png
Binary files a/docs/public/images/troubleshooting/troubleshooting-sdk-py-request-id.png and /dev/null differ
docs/public/images/troubleshooting/troubleshooting-sdk-ts-request-id.png
Binary files a/docs/public/images/troubleshooting/troubleshooting-sdk-ts-request-id.png and /dev/null differ
docs/public/images/troubleshooting/troubleshooting-tool-log-id.png
Binary files a/docs/public/images/troubleshooting/troubleshooting-tool-log-id.png and b/docs/public/images/troubleshooting/troubleshooting-tool-log-id.png differ
docs/public/images/troubleshooting/troubleshooting-trigger-id.png
Binary files a/docs/public/images/troubleshooting/troubleshooting-trigger-id.png and b/docs/public/images/troubleshooting/troubleshooting-trigger-id.png differ