Stop and start a flow without rebuilding anything
A stopped flow's nodes are built like any other flow's — being stopped means having no subscriptions, schedules or webhooks, not being absent — so a toggle only ever needed the lifecycle call and the gate that goes with it. It was doing a whole-pipeline rebuild instead, which on a populated installation is every node in every flow reconnecting. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01StpRc2C6au1WJ1EUU7fsfu
This commit is contained in:
+4
-1
@@ -13,7 +13,10 @@ Deferring because out of scope is fine, but don't mention deferring than.
|
||||
### Dashboard UI rework (dedicated session)
|
||||
|
||||
Rework the dashboard UI to make it more flexible in terms of the look and feel.
|
||||
I consider following design options a) overall appearance: material look or liquid glass (einUI https://github.com/einui/einui) b) color palette
|
||||
I consider following design options a) overall appearance: material look or liquid glass (einUI https://github.com/einui/einui) b) color palette (https://plotly.com/python/discrete-color/).
|
||||
Based on a) and b) it should be possible to derive almost endles combinations of looks.
|
||||
The color palette should affect charts/gauges and other widgets
|
||||
|
||||
|
||||
|
||||
### To be sorted
|
||||
|
||||
Reference in New Issue
Block a user