{"version":"2.1.235","anchor":"auto-reply-arming-reports-an-in-flight-wind-down-instead-of","canonical_anchor":"auto-reply-arming-reports-an-in-flight-wind-down-instead-of","heading":"Auto-reply arming reports an in-flight wind-down instead of a vague skip","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/auto-reply-arming-reports-an-in-flight-wind-down-instead-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Auto-reply arming reports an in-flight wind-down instead of a vague skip\n\nAuto-reply skip message now explains that an in-flight wind-down is blocking resubscription\n\nWhen a subscribe attempt happens while an earlier auto-reply arm is still winding down, the code now skips with the specific reason `arm_in_flight`, and the user-facing summary explains that auto-replies were not resumed because an earlier connection is still winding down, so the stop stays in place.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}