n8n | n8n@2.23.3

n8n n8n@2.23.3 released on 04-06-2026


n8n n8n@2.23.3 is out now. It fixes a core bug that could leave evaluation executions stuck in the “new” status, so operators running evaluations should apply the patch.

See the project’s GitHub compare and the referenced commit for full details: https://github.com/n8n-io/n8n/compare/n8n@2.23.2…n8n@2.23.3 (commit fde615b, issue #31702).

What’s in this release

  • Core bug fix: Prevent evaluation executions from stalling in status “new” (issue #31702).
  • Fix implemented in commit fde615b as shown in the GitHub compare view.
  • Release metadata: 2.23.3 released 2026-06-04 10:11:58; see the compare for the exact changes.

Upgrade notes

  • No schema or breaking changes; this is a patch-level bugfix and is low-risk to apply. Administrators are advised to upgrade promptly if they run evaluations or have experienced stalled executions.
  • Quick mitigation and rollback guidance: restart n8n workers or the service and clear or requeue stalled executions. Collect logs and attempt to reproduce conditions if problems persist after upgrading.

If you try the update, please share comments on your experience—either on the issue tracker referenced above or via your usual support channels.

Related posts

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...

restic | v0.19.1

restic v0 19 1: safer FUSE mounts and mountpoint checks, robust backup source and exclude handling, clearer CLI JSON output, Windows SFTP deletion fixes