The idea is:
In large workflows, it’s common to temporarily deactivate nodes in different areas while testing or debugging. Right now, you either have to:
- Manually re-enable each node one by one, or
- Shift-select and re-enable multiple nodes as long as you only select deactivated nodes.
If you drag-select an area that includes active nodes, you can’t just “enable all disabled ones” in that selection. You also still have to hunt around the canvas to find all the disabled nodes first.
As a quality-of-life improvement to reduce clicks and mouse travel, it would be great to have a UI option (button, menu action, or similar) to:
- “Enable all deactivated nodes” in the current workflow.
Optionally, it could support scope choices like:
- Enable all deactivated nodes in the entire workflow, or
- Enable all deactivated nodes in the current selection (only the deactivated nodes within whatever I’ve highlighted, even if active nodes are included in that selection).
My use case:
When I’m developing or debugging a complex workflow, I often:
- Deactivate multiple nodes across different branches to isolate a specific path.
- Later, want to go back to a “full workflow” run once I’m done testing.
At that point I have to:
- Zoom and pan around the canvas to find every deactivated node,
- Carefully shift-select only the deactivated ones (or re-enable them one by one),
- Make sure I haven’t missed anything.
On larger workflows, this becomes tedious and error-prone. A single “Enable all deactivated nodes” command would let me quickly put the workflow back into its normal, fully active state.
I think it would be beneficial to add this because:
- It saves time when switching between “debug mode” and “full workflow” mode.
- It reduces mistakes, since you’re less likely to miss a deactivated node hidden somewhere.
- It improves UX for large workflows, where bulk / smart actions are especially valuable.
Any resources to support this?
- The current editor already supports node activation/deactivation and multi-select, so this feature would build on existing concepts rather than introducing a new one.
- Similar bulk / convenience actions requested elsewhere (e.g. updating many nodes at once) show that repetitive node-level operations are a common pain point in large workflows.
Are you willing to work on this?
I’m not currently able to contribute a PR to the core codebase, but I’m happy to:
- Help refine the UX / behaviour (e.g. scope, confirmation prompts),
- Test any implementation on real-world, node-heavy workflows,
- Provide feedback on edge cases and how it feels in everyday use.