Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: Add common queries section to troubleshooting page
Adds an accordion-based "Common queries" section with how-tos for finding log IDs, auth config IDs, MCP server IDs, request IDs, and trigger IDs. Also fixes duplicate sidebar entry by removing "index" from meta.json. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 13, 2026 at 19:16 UTC
681f25821b50b29e9c1fa5fdf94e8e89984f1676
2 files changed
+43
-2
docs/content/docs/troubleshooting/index.mdx
+43
-1
@@ -7,7 +7,49 @@ import { Bug, Brain, Sparkles, MessageCircle, MessageSquare, BookOpen, Mail, Ale
7
8
This section is designed to help you quickly identify and resolve common issues encountered with Composio.
9
10
-Some quick links:
10
+## Common queries
11
+
12
+<Accordions>
13
+
14
+<Accordion title="How do I find the log ID for a failed tool execution?">
15
+Every tool execution response includes a `log_id` field. You can also find it in the [dashboard logs](https://platform.composio.dev?next_page=/logs/tools) under **Logs > Tools**. Use this ID when reporting issues to support.
16
+
17
+See [Troubleshooting tools](/docs/troubleshooting/tools#reporting-tool-issues) for more details.
18
+</Accordion>
19
+
20
+<Accordion title="How do I find my auth config ID or connected account ID?">
21
+Go to the [dashboard](https://platform.composio.dev) and navigate to **Auth Configs** for your auth config ID, or **Connected Accounts** for the connected account ID. Both IDs are visible in the detail view of each entry.
22
+
23
+See [Troubleshooting authentication](/docs/troubleshooting/authentication#reporting-authentication-issues) for screenshots.
24
+</Accordion>
25
+
26
+<Accordion title="How do I find my MCP server ID?">
27
+Your MCP server ID is the UUID in the server URL (e.g., `https://backend.composio.dev/v3/mcp/<UUID>/mcp`). You can also find it in the [dashboard](https://platform.composio.dev) under your MCP server's detail page.
28
+
29
+See [Troubleshooting MCP](/docs/troubleshooting/mcp#reporting-mcp-issues) for a visual guide.
30
+</Accordion>
31
+
32
+<Accordion title="How do I get the request ID for API debugging?">
33
+Add an `x-request-id` header with a UUID to your API request. This lets support trace your exact request in server logs.
34
+
35
+```bash
36
+curl 'https://backend.composio.dev/api/v3/tools' \
37
+ -H 'x-api-key: YOUR_API_KEY' \
38
+ -H 'x-request-id: YOUR_UUID_HERE'
39
+```
40
+
41
+Generate a UUID at [uuidgenerator.net](https://www.uuidgenerator.net/). See [Troubleshooting API](/docs/troubleshooting/api#reporting-api-issues).
42
+</Accordion>
43
+
44
+<Accordion title="How do I find the trigger ID for a trigger instance?">
45
+Go to the [dashboard](https://platform.composio.dev) and navigate to **Active Triggers**. The trigger ID is shown for each trigger instance.
46
+
47
+See [Troubleshooting triggers](/docs/troubleshooting/triggers#reporting-issues) for a screenshot.
48
+</Accordion>
49
+
50
+</Accordions>
51
+
52
+## Quick links
53
54
<Cards>
55
<Card title="Errors Reference" href="/reference/errors" icon={<AlertCircle />}>
docs/content/docs/troubleshooting/meta.json
-1
@@ -1,7 +1,6 @@
1
{
2
"title": "Troubleshooting",
3
"pages": [
4
- "index",
4
"api",
5
"authentication",
6
"cli",