> This page is for Tools.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.

# Conversation Timeouts

To ensure reliable performance and prevent indefinite waits, Moveworks enforces strict timeouts on plugin executions. These limits apply to **synchronous HTTP actions** (the most common type in plugins) and are designed to protect both your users and the platform.

# Key Timeout Limits

| Scope                         | Time Limit  | What Happens If Exceeded                                       |
| :---------------------------- | :---------- | :------------------------------------------------------------- |
| **Single plugin action step** | 30 seconds  | Likely timeout – safest target for any individual HTTP request |
| **Determined execution plan** | 45 seconds  | Certain timeout                                                |
| **Entire request lifecycle**  | 160 seconds | Certain timeout                                                |

> **Info**
>
> ***Note**: A determined execution plan is the sequence of steps the system settles on to fulfill a user request. Multiple plans may be evaluated during processing, but only one is executed*

# Recommendations

* **Target \< 30 seconds per action**: Design every synchronous HTTP call to complete well under 30 seconds. This is the most reliable guardrail, even if multiple actions run sequentially within the same step.
* **Use asynchronous patterns when needed**: For operations that may exceed 30 seconds, leverage compound actions, which are asynchronous by design.