{"version":"2.1.236","anchor":"artifact-refuses-actions-whose-target-changed-after-approval","canonical_anchor":"artifact-refuses-actions-whose-target-changed-after-approval","heading":"Artifact refuses actions whose target changed after approval","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/artifact-refuses-actions-whose-target-changed-after-approval","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Artifact refuses actions whose target changed after approval\n\nArtifact edits, replies and resolves refuse to run if the approved action was rewritten underneath them.\n\n**What**\n\nThe `live_edit`, `reply` and `resolve` Artifact actions now re-check that the approved input still names the same action before running, and refuse if a hook or permission rewrite changed it. Nothing is posted and the call can be retried so it gets checked again.\n\n**Details**\n\n- Refusals carry dedicated reason codes `live_edit_target_changed`, `reply_target_changed` and `resolve_target_changed`.\n- The existing PR-review overwrite refusal codes were folded into the same shared reason-code map.\n\n**Evidence**\n\n`` `action` no longer names what was approved \u2014 this input was approved as another Artifact action, not this reply; nothing was posted; retry so it is checked again ``\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}