Routing, skipping, and disabled nodes

Goal

Control exactly which blocks run without deleting any. Time: 10 minutes.

Ways a block doesn’t run

Cause	How it shows	YAML
Node execution is off	Still visible, marked Skipped	`enabled: false`
A decision chose another route	Skipped	—
A block before it failed	not run	—
You disconnected its only incoming wire	It’s disabled automatically and Skipped, even if file order would reach it	`enabled: false`
A `then` jumped past it	It doesn’t run	`then: <id>`

Steps

Open Decision demo from the previous lesson.
Select joined and turn Node execution off in Settings. Run the workflow: joined is shown as Skipped.
Turn it back on. Use the small × on the wire into joined to disconnect it. Because that was its only explicit incoming route, it’s disabled.
Drag from has_text’s output handle back onto joined to restore then: joined.

Note

If you disconnect a decision route, it falls through to the next block in YAML order. If a route already has a target and you choose a new node, the new node is inserted before that target.

Check your run

Runs → (latest) lists every block captured at the start. Disabled and unrouted blocks are visible with their skipped or not-run state.

Exercise

Write a YAML fragment where block a jumps straight to c, so that b never runs, without using a decision.

Details

- id: a
  kind: http
  url: mock://a
  then: c
- id: b
  kind: http
  url: mock://b
- id: c
  kind: http
  url: mock://c