New Code-Node crashes workflow if running after old function-node (latest version)

Hey, firstly thank you for your great work with n8n, and the countless time you all helped us out when having issues with nodes or our setup, or when having problems realizing ideas in N8N.

Today I discovered, what I think is a bug: The new code-node returns an error, if running after an old function node. The error is: ERROR: Unknown top-level item key: index [item 0]

I’ve made this simple workflow for you to try:

We are mainly using the old function node in old workflows, that we’re extending with new workflows (execute Workflow-Node) after the updates. We’ve also discovered that the old function-node just runs faster when provided with large amounts (multiple mb) of data.

Information on my n8n setup

  • n8n version: latest, 0.210.2
  • **Database you’re using (default: SQLite): Postgres
  • **Running n8n with the execution process [own(default), main]: own
  • **Running n8n via [Docker, npm,, desktop app]: Docker

Using a combination of old and new code- / function-nodes worked in previous versions, like version 0.204.0.

Thank you for your time and have a nice evening!


Hey @one_juru,

That is a good find thanks for reporting it, I have created an internal ticket which we will be tracking as NODE-171.


Thank you for the quick response :slight_smile:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.