{"version":"2.1.238","anchor":"clearer-reasons-when-auto-replies-cannot-be-resumed","canonical_anchor":"clearer-reasons-when-auto-replies-cannot-be-resumed","heading":"Clearer reasons when auto-replies cannot be resumed","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/clearer-reasons-when-auto-replies-cannot-be-resumed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Clearer reasons when auto-replies cannot be resumed\n\nAuto-reply resume failures now say whether arming is still in progress or watch state was incomplete.\n\n**What**\n\nResuming automatic replies to artifact comments now reports two specific outcomes that previously fell through to vaguer ones: arming is still in progress, in which case `\/tasks` will show whether it came back, and the conversation's saved watch state was incomplete.\n\n**Details**\n\n- The \"not stopped\" message now also explains that a pause caused by an interrupt lifts on the user's next message.\n\n**Evidence**\n\n`are still starting up; \/tasks will show whether they came back.`\n\n- Area: Artifacts\n- Names: `\/tasks`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}