Increase API timeout from 2 to 5 minutes for generation requests #607
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.
Client-side streaming requests were timing out at 2 minutes when processing documents with complex prompts. Server-side timeout was even shorter at 1 minute.
Changes
Client (
client/src/api/client.js)STREAMING_REQUEST_TIMEOUT: 120000ms → 300000msServer (
server/config.js)REQUEST_TIMEOUTdefault: 60000ms → 300000msBoth timeouts now allow 5 minutes for LLM generation, with inline comments documenting the duration. Server timeout is configurable via
REQUEST_TIMEOUTenvironment variable.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.