{"version":"2.1.224","anchor":"409-conflicts-read-their-cause-from-a-header","canonical_anchor":"409-conflicts-read-their-cause-from-a-header","heading":"409 conflicts read their cause from a header","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/409-conflicts-read-their-cause-from-a-header","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### 409 conflicts read their cause from a header\n\nConflict responses now read their cause from a header, distinguishing a live worker from a stale registration.\n\n**What**\n\nConflict responses are now attributed from an `x-ccr-conflict-reason` header, falling back to parsing the reason out of the JSON body, which separates being superseded by a live worker from a stale registration with no successor.\n\n**Evidence**\n\n`x-ccr-conflict-reason`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}