n8n Zero to Hero · Level 1: The Automation Playground · Episode 08
Oops! Fixing Broken Blocks
Two different ways an expression can break — one silent, one loud — plus a setting that retries for you and a trick that saves you from re-running everything.
What this episode is about
Every builder breaks something eventually — today we do it on purpose, twice. First we reference the wrong field on a correct node and get a quiet "undefined" with no error at all. Then we misspell the node name itself — id cards instead of id card — and get a loud error: "the node doesn't exist," visible in the execution details. We fix both, then turn on Retry On Fail so a node attempts a few times before giving up instead of failing immediately, and finish with Pin Data: freezing a node's output so you can test the nodes after it without re-running your whole workflow every single time.
What you'll learn
- Why a wrong field name gives you a silent "undefined" instead of an error
- Why a misspelled node name gives you a loud error instead
- Reading the actual error message in the execution details panel
- Turning on Retry On Fail and setting Max Retries so a node tries again before failing
- What Pin Data does, including the P keyboard shortcut, and why it saves you time while testing