{"version":"2.1.236","anchor":"clearer-rules-about-what-an-interrupt-does-to-an-artifact-wa","canonical_anchor":"clearer-rules-about-what-an-interrupt-does-to-an-artifact-wa","heading":"Clearer rules about what an interrupt does to an artifact watch","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/clearer-rules-about-what-an-interrupt-does-to-an-artifact-wa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Clearer rules about what an interrupt does to an artifact watch\n\nAfter an interrupt you are told the artifact watch stopped and what re-arms it.\n\n**What**\n\nThe guidance shown after you interrupt now states that the interrupt stopped the watch, that publishing because you asked re-arms it, and that publishing unasked leaves it stopped.\n\n**Details**\n\n- A consent explanation is corrected to say republish notifications carry no content.\n- Resuming a session restores at most the watch on the most recently used artifact.\n\n**Evidence**\n\n`publishing ${n} without being asked \\u2014 while handling a notification or a wake-up \\u2014 leaves ${n} stopped.`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}