Artifact sweep keeps digests named in node settings

A Service's weights or a wren node's model held only in a setting were swept once the run that produced them was deleted.
2026-10-24 21:28:35 +02:00
parent aa49972087
commit 6892651e76
5 changed files with 43 additions and 12 deletions
@@ -180,9 +180,10 @@ superusers may see answers 403 to anyone else for the frames its messages
 hold, the last 8 included (see [Who may watch a camera](../interface/dashboards.md#who-may-watch-a-camera)).

 A superuser can remove stored bytes with `DELETE /artifacts/<digest>`. While
-a run, a current message or a flow input's initial value still references the
-digest, the call returns `409`. The hourly sweep removes unreferenced bytes
-on its own, so this is for reclaiming space sooner.
+a run, a current message, a flow input's initial value or a node setting in a
+published or draft flow still references the digest, the call returns `409`.
+The hourly sweep removes unreferenced bytes on its own, so this is for
+reclaiming space sooner.

 ## Dashboards and devices