Previously, if you wanted to temporarily skip a step in your CloudFlow — for debugging, testing a subset of your workflow, or iterating on a design — you had to delete the node and recreate it later. This meant losing your configuration and having to rewire transitions. You can now disable individual steps in your CloudFlows without deleting them by right-clicking any step in your CloudFlow and selecting "Disable Step" to toggle it off. Disabled steps in the flow are:

• Visually dimmed so you can see at a glance which steps are active
• Skipped during execution — downstream steps continue to run normally
• Excluded from validation — errors on disabled steps won't block publishing
• Hidden from reference pickers — other steps can't accidentally reference a disabled step

Re-enable a step at any time with a single click.

Smart reference handling

If other steps reference the one you're disabling, CloudFlow will display a confirmation dialog. If you proceed, downstream references are automatically cleaned up, and affected steps are flagged so you know exactly what to fix.

Run history

Disabled steps appear with a "Skipped" status in run history, giving you a complete picture of every execution — including what was intentionally bypassed.

Note: Trigger and branch nodes cannot be disabled, as they are structural elements of the flow.