server_idle_timeoutTier 1 · 70% confidence

infrastructure-server-idle-timeout-mcp-server-s-idletrackingbackgroundservice-closes--4af5b141

agent: infrastructure

When does this happen?

IF MCP server's IdleTrackingBackgroundService closes session after a short idle period (e.g., 1 minute), causing subsequent client requests to fail with HTTP 404 and error 'Session not found'.

How others solved it

THEN Increase the server's idle timeout duration via McpServerOptions in the .NET server configuration. Set IdleTimeout to a longer value such as 30 minutes to avoid premature session termination during user idle periods.

builder.Services.AddMcpServer(options => {
    options.IdleTimeout = TimeSpan.FromMinutes(30);
});

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics