@devries-cameron20 / composio Mirror · read-only
Fork 0

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 21, 06:00 UTC

next
md 27 lines 1.37 KB
Rendered Raw
1 ## Use Logs for execution evidence
2
3 Open **Platform → Logs** and choose the tool or trigger log view. Filter by the
4 smallest known non-secret identifier, then open the row to inspect its status,
5 toolkit, action or trigger, version, user, connection, request/response or
6 provider error, timing, and correlation IDs.
7
8 Use a **Log ID** for a tool execution, a **Trigger ID** plus Log ID for a
9 trigger event, and a **Session ID** for session behavior. Never request API
10 keys, access or refresh tokens, provider client secrets, webhook secrets, or
11 passwords.
12
13 ## Use Users and Sessions to explain retrieval and execution context
14
15 Open **Users** to find a project user and its connected accounts, triggers,
16 sessions, and filtered logs. Open **Sessions** to inspect session toolkits,
17 connection behavior, and execution timeline. An active connection elsewhere in
18 the organization does not prove it was eligible for this session: project,
19 `user_id`, toolkit restrictions, auth-config selection, and explicit connected
20 account selection all affect resolution.
21
22 ## Disable a trigger when the goal is to pause it
23
24 Open **Triggers** to inspect status and related logs. Disable a trigger when it
25 should pause temporarily; delete it only when the subscription should be
26 removed. Before recreating a trigger, verify the selected project, user,
27 connected account, trigger type, and current provider event support.