Unhandled IF branch in n8n
Why disconnected IF branches silently drop data
What is this issue?
An IF node has two outputs: true and false. When the false branch is not connected to any node, items that don't match the condition are silently dropped from the workflow without any error or warning.
Common unhandled patterns:
•IF node with only 'true' output connected•Condition assumes all items pass but some fail•Filter logic that accidentally discards valid data•Edge cases not considered in the condition
Why is this dangerous?
Silent data loss
Items that don't match simply disappear. You won't know data was lost.
Incomplete processing
A subset of your data is processed while the rest is silently discarded.
Hard to debug
Since there's no error, you only discover the issue when checking final results.
Unexpected behavior
Data format changes can cause previously passing items to fail the condition.
How to fix it
- 1
Connect both branches
Always connect both true and false outputs, even if one goes to a 'do nothing' path.
- 2
Add logging for false branch
At minimum, log items that hit the false branch to understand what's being filtered.
- 3
Handle false cases explicitly
If false cases are expected, process them appropriately (alternative flow, different processing, etc.).
- 4
Review your conditions
Ensure conditions cover all expected cases and handle edge cases like null or empty values.
Scan your workflow now
Upload your n8n workflow JSON and detect IF nodes with unconnected false branches.