Add explicit request timeout to WorkIQ MCP server configs - #185
Open
Tolga Kilicli (tolgaki) wants to merge 1 commit into
Open
Add explicit request timeout to WorkIQ MCP server configs#185Tolga Kilicli (tolgaki) wants to merge 1 commit into
Tolga Kilicli (tolgaki) wants to merge 1 commit into
Conversation
Declare a 300s request timeout for the workiq and workiq-preview MCP servers. Without it, a stalled tool call has no client-side bound. 300000 ms matches the service's server-side response ceiling, so it does not truncate any call that would otherwise succeed. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
Adds a
timeoutto theworkiqandworkiq-previewMCP server definitions."oauthPublicClient": true, + "timeout": 300000, "auth": {Why: neither config declared a request timeout, so a stalled tool call had no client-side bound.
Why 300000 ms: it matches the service's server-side response ceiling, so it will not truncate a call that would otherwise have completed.
Note: not all MCP clients currently enforce a per-server timeout, so the practical effect varies by client. The value is correct regardless and takes effect wherever the field is honored.