@Steve-Mcl As I've said, we will introduce the ability to disable any node.
It doesn't require any special nodes in your flow. It doesn't require any changes to the structure of your flow when you realise you want to disable something.
It does require a deploy. It may not be exactly what you want, but it is something that will address a number of requests and use cases.
You've said a few times that your proposal would not take much doing.
That simple isn't the case. We have no precedent for having a node in the middle of a flow that has a button or state that can be toggled in the editor without a deploy. The UI design work to get that right is not trivial.
I understand what functionality you want. I'm not ignoring it. But I do have to align it with work we already have underway and work we have planned.
Further down the line we have plans for a flow debugger (after 1.0 ships). I would not want to rush something in now that introduces new UI concepts at this stage of getting to 1.0, particularly when it overlaps with a whole area of functionality we want to focus on later this year.
But it certainly feeds into the bucket of functionality the flow debugger can enabled.
