different-ai/openwork · error

MCP_REQUEST_TIMEOUT

MCP_REQUEST_TIMEOUT

Error message

MCP_REQUEST_TIMEOUT

What it means

Error "MCP_REQUEST_TIMEOUT" thrown in different-ai/openwork.

Source

Thrown at ee/apps/den-api/src/capability-sources/external-mcp-diagnostics.ts:1235

  const code = errorCode(error)
  if (code) {
    const classified = classifyByCode(code)
    if (classified) return classified
  }

  const providerAuthorization = providerAuthorizationRequired(error)
  if (providerAuthorization) {
    return providerAuthorizationClassification(providerAuthorization.connectUrl)
  }

  const numericCode = numericErrorCode(error)
  if (numericCode === -32001) {
    if (!localRequestTimeout(error)) return providerDeclaredErrorClassification()
    return {
      phase: fallbackPhase,
      category: "request_timeout",
      code: "MCP_REQUEST_TIMEOUT",
      retryable: true,
      actionOwner: "provider_admin",
      operatorAction: "Check provider latency and retry after the current MCP request can complete within its bounded timeout.",
    }
  }
  if (numericCode === -32602 && fallbackPhase === "MCP_TOOL_EXECUTION") {
    return {
      phase: "MCP_TOOL_EXECUTION",
      category: "mcp_tool_input_invalid",
      code: "MCP_INVALID_PARAMS",
      retryable: false,
      actionOwner: "openwork",
      operatorAction: "Correct the tool arguments using the latest advertised input schema; do not retry the same arguments unchanged.",
    }
  }
  if (numericCode !== undefined) return providerDeclaredErrorClassification()

  const name = errorName(error)

View on GitHub (pinned to 2b7df46e8a)

When it happens

Trigger: Thrown at ee/apps/den-api/src/capability-sources/external-mcp-diagnostics.ts:1235 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

AI-assisted analysis of different-ai/openwork@2b7df46e8a (2026-09-01). Data as JSON: /api/errors/11aba46d9cb8b34a. Report an issue: GitHub.