Pause Workflow Actions in Sparkforge: Enable/Disable Nodes

By Sparkforge Support Team ·Last reviewed May 3, 2026

Pause Workflow Actions toggles individual workflow nodes on or off in both Advanced and Standard Builder. Disabled nodes are skipped at runtime so you can test variations without rebuilding connections.

Pause Workflow Actions lets you temporarily turn workflow nodes on or off. Disabled nodes are skipped during execution, so you can debug, A/B-test, or iterate without losing the original setup.

What it does

  • Pause without breaking: turn off individual nodes to test variations or isolate issues.
  • Non-destructive: wiring stays intact — no need to remove or rebuild connections.
  • Clear visuals: disabled steps dim on the canvas and skip at runtime.

Why it helps

  • Works in both builders: available in Advanced and Standard Builder.
  • Faster testing: disable a step, run, re-enable.
  • Zero rebuilds: configurations stay intact.
  • Clean execution: contacts never stall on a disabled node.
  • Safer iteration: A/B-test without affecting production logic.

How to disable a node

  1. Hover any node in the Advanced or Standard Builder.
  2. Click the pause icon (Enable/Disable toggle).
  3. The node greys out and adds a Disabled label.
  4. Toggle back on to restore execution.

Execution behavior

  • Disabled nodes appear dimmed with a Disabled tag and are skipped automatically — even when they're the only forward path.
  • Downstream actions still fire on any active path reachable from the current step.
  • Re-enabled nodes execute exactly as configured.

Frequently Asked Questions

Will contacts get stuck at a disabled node?
No. Sparkforge automatically skips disabled nodes and continues down any active path.
Can I disable an entire branch?
Yes. Toggle off each node in the branch. All disabled nodes will be skipped until re-enabled.
How is this different from Pause Workflows on Certain Dates?
Pause Workflow Actions disables individual steps inside a workflow. Pause Workflows on Certain Dates pauses entire published workflows for date ranges.
Do disabled nodes count toward execution limits?
No. Disabled nodes are skipped at runtime and do not consume executions.
Can I bulk-enable or disable nodes?
Not at launch. Toggling is one node at a time. Bulk actions are on the roadmap.
Will execution logs show skipped nodes?
Yes. Logs mark disabled nodes as Skipped for traceability during testing.

Was this article helpful?

Related Articles