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
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Tool Execution Retries" |
| 4 | description: "Public support knowledge for Tool Execution Retries." |
| 5 | category: "sessions-and-execution" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "sdk" |
| 10 | - "tool-execution-retries" |
| 11 | --- |
| 12 | # Tool Execution Retries |
| 13 | |
| 14 | ## Current SDKs do not automatically retry non-idempotent tool executions |
| 15 | |
| 16 | Python SDK 0.16.0 and TypeScript SDK 0.14.0 changed tool execution and Proxy Execute so non-idempotent writes are not automatically retried after timeouts, rate limits, or server errors. Upgrade to at least those versions before diagnosing duplicate sends or writes as current SDK retry behavior. |
| 17 | |
| 18 | An ambiguous client timeout still does not prove that the provider-side action failed. Before manually retrying a send, create, update, or delete action, inspect the execution log or provider state to determine whether the first attempt completed. If duplicates persist on a current SDK, collect the SDK version, execution log IDs, and timestamps for support. |
| 19 | |
| 20 | Suggested guidance: |
| 21 | |
| 22 | ```text |
| 23 | Current Composio SDKs do not automatically retry non-idempotent tool executions. A timeout can still be ambiguous, so check the execution log or provider state before manually retrying an action that may have completed. |
| 24 | ``` |