Fix: Increase MCP Client Timeout to Prevent Processing Errors #29
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.
This PR addresses the recurring timeout error where processing larger documents fails after 30 seconds. The error
mcp.shared.exceptions.McpError: Timed out while waiting for response to ClientRequestoccurs during theextract_file_datastep because the server-side processing takes longer than the client's default timeout.Before:
After:
The Fix
This is a quick-fix that increases the timeout for the
BasicMCPClientfrom 30 seconds to 120 seconds. This provides a more generous and stable window for the server to complete its work, preventing the premature timeout and improving the user experience.Future Work
While this hot fix immediately resolves the issue for users, a more robust long-term solution can still be explored. Potential improvements include:
extract_file_dataworkflow to reduce processing time.I'll start working on this, but in the meantime, this hot-fix should resolve our current issues.
Related Issues