Suddenly "Cannot assign to read only property ... " + "Referenced node is unexecuted"

Hey there everyone,
since 9.00 am this morning some issues occurred on our n8n setup.
Before consulting a freelancer / whatever … your advice would be helpful as it happened out of nowhere to smoothly flowing workflows.

Describe the problem/error/question

  • Over 10-20 workflows we use “execute workflow”-nodes to jump to this one:
  • It takes a section name from the mother workflow and moves an asana task to that section
  • Mother-WF = ‘Section A’ ; Sub-Worklow = actually moves task to section A
  • now this sub-wf stopped working, though it’d been running for months
  • Problematic is a custom code node:

let items = $items(“Input”);
let target_section_name = items[0].json.target_section_name;
for (const item of $input.all()) {
item.json.data = item.json.data.filter(d => d.name.trim().toLowerCase() === target_section_name.trim().toLowerCase() );
}
return $input.all();

  • So how do we get that running again?

What is the error message (if any)?

Cannot assign to read only property ‘name’ of object ‘Error: Referenced node is unexecuted’

Please share your workflow

Share the output returned by the last node

  • at least that’s the output from the main workflow
  • [{“data”: {},
    “target_section_name”: “Content Beschaffung 🕵🏼‍♀️”,
    “gid”: 1209248935965501,
    “resource_type”: “task”}]

Information on your n8n setup

  • n8n version: => just the saas, nothing self hosted

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
  • n8n version: 1.75.2
  • Database (default: SQLite): Default => : SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): /
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: MacOS (again, doesnt matter, as it’s about cloud and no problem regarding ux)

hi @PaulV

Welcome to the community! The code doesn’t look complex indeed and I see no immediate reason why this started failing, assuming you haven’t made any change as you mention.

Maybe the object passed on to the node changed its structure? Can you compare a working vs failed execution to see if the data has the same structure?

Does the previous execution also work the same way as it did (i.e. same nodes, and output between each node)?

Thanks!