{"version":"2.1.235","anchor":"resume-replies-gains-an-arm-in-flight-refusal-and-a-watch-st","canonical_anchor":"resume-replies-gains-an-arm-in-flight-refusal-and-a-watch-st","heading":"resume_replies gains an arm_in_flight refusal and a watch-stop explanation","tier":"internal","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/resume-replies-gains-an-arm-in-flight-refusal-and-a-watch-st","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### resume_replies gains an arm_in_flight refusal and a watch-stop explanation\n\nresume_replies now refuses to attach to an in-flight watch and explains when a watch stop is blocking a resume\n\nThe artifact auto-reply resume path adds a new refusal case: if a live-watch connection started before the watch was stopped and is still winding down, a resume cannot attach to it (`arm_in_flight`). Separately, when it's the artifact's own watch stop, rather than a separate auto-reply stop, that's holding replies back, resume now denies with a decision reason stating that only an approved re-watch can clear it, and the permission description tells the user that resuming will also re-watch.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}