{"version":"2.1.271","anchor":"watch-cap-error-message-explains-displacement-priority","canonical_anchor":"watch-cap-error-message-explains-displacement-priority","heading":"Clearer guidance when an artifact watch hits its cap","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/watch-cap-error-message-explains-displacement-priority","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Clearer guidance when an artifact watch hits its cap\n\nThe message shown when a session hits its artifact-watch limit now better explains how to make room, favoring republishing over stopping another watch\n\n**What**\n\nWhen a session already holds the maximum number of artifact watches (a limit called `watch_cap`), the error\/status messages shown have been reworked to be clearer about what to do next.\n\n- The message now explains that a new publish can displace an idle watch, but a plain watch request cannot.\n\n- The comment-watch-can't-resume message was reworded: it now tells you to simply republish (open the session and publish again) as the primary suggestion, with the old advice to explicitly stop watching another artifact demoted to a fallback (\"If that's refused too...\").\n\n**Why**\n\nThis makes it clearer why a watch request was denied and gives a more useful first suggestion for resolving it, instead of leading with the more disruptive option of stopping another watch.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}