{"version":"2.1.224","anchor":"remote-worker-conflicts-say-whether-the-registration-was-sta","canonical_anchor":"remote-worker-conflicts-say-whether-the-registration-was-sta","heading":"Remote worker conflicts say whether the registration was stale or superseded","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-worker-conflicts-say-whether-the-registration-was-sta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote worker conflicts say whether the registration was stale or superseded\n\nWorker registration conflicts now say whether the registration was stale or superseded.\n\n**What**\n\nWhen the server rejects a worker registration with HTTP 409, Claude Code reads the reason from the response and reports either a stale registration with no live successor or being superseded by a newer worker, instead of one generic conflict.\n\n**Details**\n\n- The two outcomes log separately as `cli_worker_epoch_stale` and `cli_worker_epoch_mismatch`.\n- Reading the response body is skipped when the client has already closed.\n\n**Evidence**\n\n`cli_worker_epoch_stale`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}