You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.271,
ImprovementsSection of the release
What
When 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.
The message now explains that a new publish can displace an idle watch, but a plain watch request cannot.
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...").
Why
This 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.
