Flow delete offers to delete its runs, history included
DELETE /runs?flow= removes every Run row of the flow but left its flow_run rows, so a deleted flow kept appearing in the history. history=true now drops those too, and the flow delete dialogs (editor and bulk) send it when "Also delete its runs" is ticked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx
This commit is contained in:
+1
-1
@@ -131,7 +131,7 @@ values. You can publish only to declared messages, just as dashboard controls do
|
||||
| `GET` | `/runs/{id}/nodes/{node}/outputs` | read what one node returned |
|
||||
| `POST` | `/runs/{id}/cancel`, `/runs/{id}/retry` | cancel, or create a retry |
|
||||
| `DELETE` | `/runs/{id}` | delete a finished run and its records |
|
||||
| `DELETE` | `/runs?flow={name}` | delete a flow's runs; refused while any are active |
|
||||
| `DELETE` | `/runs?flow={name}` | delete a flow's runs; refused while any are active. `history=true` also clears its cascades from the history |
|
||||
| `GET` | `/runs/{id}/metrics?name=&stride=` | read metric series |
|
||||
| `GET` | `/runs/metrics/names` | list metric names across a selection |
|
||||
| `GET` | `/runs/series/compare?ids=a,b,c&metric=&x=` | compare curves by step, time, or another metric |
|
||||
|
||||
@@ -191,9 +191,11 @@ Select two or more runs to compare curves and the parameters that differ.
|
||||
Plot against step, elapsed seconds or another metric from the same runs.
|
||||
Comparisons have shareable URLs.
|
||||
|
||||
Deleting a flow keeps its run history. You can still inspect those runs, but
|
||||
cannot retry them until the flow exists again. Delete history separately,
|
||||
after active runs finish or are cancelled.
|
||||
Deleting a flow keeps its run history, and the artifacts those runs recorded
|
||||
stay on disk. You can still inspect those runs, but cannot retry them until
|
||||
the flow exists again. Tick **Also delete its runs** in the delete dialog to
|
||||
clear them with the flow, or delete history separately after active runs
|
||||
finish or are cancelled.
|
||||
|
||||
### Taking it into a dataframe
|
||||
|
||||
|
||||
Reference in New Issue
Block a user