{"version":"2.1.300","anchor":"mcp-task-polling-detects-sign-in-refusal","canonical_anchor":"mcp-task-polling-detects-sign-in-refusal","heading":"Long-running MCP tasks stop with a clear message when sign-in is refused","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/mcp-task-polling-detects-sign-in-refusal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Long-running MCP tasks stop with a clear message when sign-in is refused\n\nWhen an MCP server refuses sign-in while Claude Code checks on a long task, checking stops with a message saying the poll was refused\n\n**What**\n\nSome MCP servers, add-on programs that give Claude extra tools, run long tasks. Claude Code repeatedly asks the server how such a task is going, which is called polling.\n\nWhen the server refuses one of these checks because the sign-in is no longer accepted, Claude Code now stops polling and reports that a poll of the task was refused. The status can later read \"the sign-in is accepted again\" once the refusal clears. Errors the server actually answered with also now get their own failure message.\n\nBefore, the only failure was \"Lost contact with task\" after several checks failed.\n\n**Why**\n\nIf your access to an MCP server is withdrawn mid-task, you find out quickly and see that sign-in is the problem, instead of waiting for a generic lost-contact error.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}