Not sure if this is intended behavior but when I have an error in the Edit Fields node it outputs as part of the output branch and not the error branch (when continue with error branch is enabled). I also have a broader question about testing errors - ie how would I simulate in error with any node to set my error checking logic up?
There is a syntax error (e.g. {{ $json.locatio }} with a misspelled closing brace) in an Edit Fields node, execution is not branched to the Error Branch even when it is enabled.
This is not a bug — it is designed into some nodes like Set, Edit Fields, and other “transformer” nodes in n8n.
Nodes like Edit Fields don’t throw an exception that interrupts the flow, but rather internally capture the expression evaluation error and include it as part of the output object, especially when:
The “Continue On Fail” option is implicit (even if it’s not visible),
The node isn’t configured to force an error.
In these cases, n8n considers the node execution “successful,” even with errors in the data, and therefore continues on the Success branch.
@Erick_Torres Thank you for the quick answer. My syntax error was intentional to try and trigger the error branch but I guess that makes sense. Do you know if there is someway to trigger a test error of a node to get it’s structure (in my case for logging) or is there some sort of unified error structure that each node follows?
