{"version":"2.1.238","anchor":"mcp-retry-and-reconnect-stop-when-the-account-changes-during","canonical_anchor":"mcp-retry-and-reconnect-stop-when-the-account-changes-during","heading":"MCP retry and reconnect stop when the account changes during backoff","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/mcp-retry-and-reconnect-stop-when-the-account-changes-during","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### MCP retry and reconnect stop when the account changes during backoff\n\nMCP retries are abandoned if you switch accounts during the backoff wait.\n\n**What**\n\nThe retry loop for remote MCP servers that failed transiently now snapshots the signed-in account before backing off and abandons the queued retries if it changed, because those rows belong to the previous account. This applies on every retry, with no flag.\n\n**Details**\n\n- The loop only re-attempts servers whose remembered connect result was actually discarded, and skips the round trip entirely when none were.\n- The reconnect path captures the account before its retry timer and returns early if it no longer matches.\n- The connector-connect path likewise discards results superseded by a newer attempt.\n\n**Evidence**\n\n`[MCP] Retry: identity changed during backoff, stopping (these rows belong to the previous account)`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}