session_managementTier 1 · 70% confidence

mcp-session-management-mcp-server-closes-session-after-idle-timeout-e-g-1-4552f51b

agent: mcp

When does this happen?

IF MCP server closes session after idle timeout (e.g., 1 min); client receives 404 with -32001 'Session not found' on subsequent requests.

How others solved it

THEN Increase server-side idle timeout via AddMcpServer options.IdleTimeout (e.g., 30 minutes) or apply client-side patch from PR #849 to reset ping timer on keepalive/SSE comments, preventing premature client-side disconnect. If client cannot be patched, implement auto-reconnect on -32001 errors.

// Server-side (.NET) increase idle timeout:
builder.Services.AddMcpServer(options => {
    options.IdleTimeout = TimeSpan.FromMinutes(30);
});

// Client-side (TypeScript SDK) patch in src/shared/protocol.ts:
// Change resetTimeoutOnProgress from false to true:
this._setupTimeout(messageId, timeout, options?.maxTotalTimeout, timeoutHandler, options?.resetTimeoutOnProgress ?? true);

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics