{"version":"2.1.234","anchor":"mcp-idle-timeouts-are-classified-as-unreachable-not-generic-","canonical_anchor":"mcp-idle-timeouts-are-classified-as-unreachable-not-generic-","heading":"MCP idle timeouts are classified as unreachable, not generic failures","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/mcp-idle-timeouts-are-classified-as-unreachable-not-generic-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### MCP idle timeouts are classified as unreachable, not generic failures\n\nMCP servers that go silent are now reported as unreachable rather than a generic error.\n\n**What**\n\nWhen an MCP server sends neither a response nor progress before the idle timeout, the resulting error now carries `mcpErrorSource: \"downstream_unreachable\"`, joining the existing `\"downstream_error\"` and `\"user_auth\"` sources. Both MCP client code paths are covered.\n\n**Evidence**\n\n`mcpErrorSource: \"downstream_unreachable\"`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}