fix/agent-mcp-tool-timeout - #176
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix: Agent MCP tool calls now honor the MCP connection's own Timeout(s) : #173
The Agent node used the MCP connection's timeoutSeconds only for tool discovery (_list_mcp_tools), but the actual call_tool execution was always given the agent-level toolTimeoutSeconds instead. So setting MCP Timeout(s) = 1800 had no effect on long-running tool calls; they were bounded by the agent timeout (capped at 300 in the UI), which is why calls failed around the 5-minute mark.