{"version":"2.1.274","anchor":"artifact-copy-from-action-gated-behind-a-frozencombined-f","canonical_anchor":"artifact-copy-from-action-gated-behind-a-frozencombined-f","heading":"Artifact 'copy_from' action gated behind a frozen\/combined feature check","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-copy-from-action-gated-behind-a-frozencombined-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact 'copy_from' action gated behind a frozen\/combined feature check\n\nArtifact copy_from now also requires a combined feature check, or it fails outright\n\n**Unclear.** What the two underlying checks (Qst and pme) actually gate is not stated.\n\n**What**\n\nThe `copy_from` action, which copies assets (like files or images) directly between artifacts on the server, now requires two internal feature checks to both pass before it can run. If either check fails, the action is refused with an explicit message saying it is not enabled for the account, instead of running or falling back to the older permission-rule checks alone.\n\n**Why**\n\nThis adds another gate on top of the deny\/ask permission-rule checks introduced previously, so `copy_from` can be turned off for an account independently of those rules.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}