n8n, the workflow automation platform, has released version 2.23.3 with a targeted fix for a nagging issue: evaluation executions getting stuck in a "new" state. The patch, out June 4, 2026, addresses a core bug that could leave automations hanging indefinitely.
The update resolves a problem where evaluation executions—those that run conditional logic or test expressions—would stall while in status 'new'. This isn't a minor annoyance. Stalled executions can cascade, blocking downstream processes and creating delays in time-sensitive workflows.
The fix, tagged commit fde615b, targets the core engine. The exact mechanism isn't fully detailed, but the solution likely involves tweaking the internal state machine for how n8n processes execution queues. Essentially, a race condition or deadlock was preventing evaluation tasks from transitioning out of the initial queued state.
For teams relying on n8n for production workflows, this is a silent killer. You might not notice a stalled evaluation immediately—it just sits there, waiting. But eventually, your pipeline grinds to a halt. This fix directly improves reliability without adding complexity or new features.
What's interesting is the narrow scope. This isn't a massive refactor; it's a focused surgical strike. That's good engineering. It means the dev team is paying attention to edge cases that actually bite users. And in the world of automation, where trust in your tools is everything, these small patches build confidence.
If you've ever wondered why an n8n workflow just stopped executing without errors, this might be why. Upgrading is straightforward, and the fix requires no configuration changes. Just deploy and move on.
Official Source: https://github.com/n8n-io/n8n/releases/tag/n8n%402.23.3