How can I resolve the 'Cannot assign to read only property "name"' error in my n8n workflow?

Below is some guidance based on similar documentation on how to troubleshoot errors when a node reference is unexecuted.

---

What’s Happening

The error

JSCopied
Cannot assign to read only property 'name' of object 'Error: Referenced node is unexecuted'

indicates that an expression is referencing a node that hasn’t executed yet. Even if you see that "Wake Get Orders" was executed several times, the error can be thrown when:

• The workflow’s execution order isn’t ensuring that all values are available at the time that your code runs.
• A referenced node’s output is missing or has not been passed along properly.

---

Troubleshooting Steps

1. Verify Execution Order
   Check that your workflow is wired so that "Wake Get Orders" executes before the node where you access its output. In some cases a re-configuration or wiring change—even if the node executed in a previous run—could alter the runtime order.

2. Test the Node in Isolation
   As a first troubleshooting step, manually trigger the workflow up to the "Wake Get Orders" node. Confirm that its output is exactly what you expect before it is passed to the code node.

3. Double-Check Expression Usage
   The error message might also occur if the code is trying to modify a read-only property (for example, inadvertently changing the node’s name) while deriving the list of orders. Ensure that your code only reads from the node:

   JSCopied
   const allOrders = $items("Wake Get Orders").map(item => item.json);

   If you need to process data further, work on a shallow or deep clone of the data to avoid writing to properties that are read-only. For example:

   JSCopied
   const allOrders = $items("Wake Get Orders").map(item => ({ ...item.json }));

4. Check for Typos
   Ensure that the node name within the expression is an exact match. Even a minor spelling or case mismatch can lead n8n to think the node hasn’t been executed.

5. Consider Workflow Adjustments
   If the error persists, consider adding a Wait node (or similar mechanism) to give enough time for the API call and subsequent processing before referencing the node’s output.

---

In Summary

The error is generally tied to referencing an output that isn’t ready at the moment your code runs. You should:

• Confirm the correct execution order.
• Check that the exact node name is used.
• Clone data if you plan to modify it.
• Optionally add buffering (e.g., a Wait node) to ensure that outputs are available.

This approach should help you isolate and resolve the error in your workflow. Happy troubleshooting!

Based on the error message you’re seeing, it appears that one of your expressions is trying to use output from a node that hasn’t executed during that workflow run. Although you mentioned the “Wake Get Orders” node executes seven times, the error:

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

indicates that at least one of the executions (or one branch of your workflow) did not actually produce the output you expect. Here are some steps you can follow to troubleshoot and resolve this issue:

---

1. Verify Node Execution Order

Check that the node you’re referencing—“Wake Get Orders”—is guaranteed to run before your code snippet is executed. In some cases, conditionals (like your Switch node) or batch splits may cause one branch not to execute under certain conditions. You can test the execution order by using the node’s execution status.

For example, in a JavaScript code block, you can check:

JSCopied
if (!$node["Wake Get Orders"].isExecuted) {
  throw new Error("Wake Get Orders node hasn’t executed yet");
}

This way, you can conditionally handle the situation rather than trying to map over a non-existent output.

---

2. Confirm Data Existence for All Batches

Since you’re using a Split In Batches node, it’s possible that at least one batch might not have any data coming from “Wake Get Orders.” Make sure your code accounts for the possibility of an empty or undefined output. For instance:

JSCopied
const items = $items("Wake Get Orders");
if (items.length === 0) {
  throw new Error("No items found from 'Wake Get Orders'.");
}
const allOrders = items.map(item => item.json);

This check ensures you’re not processing an empty array or accessing properties on an object that wasn’t produced by an executed node.

---

3. Check Conditional Paths

Since your workflow uses a Switch node to determine the platform and route API requests, verify that all possible branches lead to an execution of “Wake Get Orders” when needed. Even though you see several executions, there might be one of the conditions (or a fallback case) where the node isn’t run, leading to this error when your code tries to access its data.

---

4. Review Recent Changes or Updates

If the workflow was working before and the error started appearing recently, look for any recent changes in node configurations or expressions. Even small adjustments to the workflow can alter execution logic, resulting in expected nodes not running in some cases.

---

Final Thoughts

Ensure that your workflow’s wiring and logic ensure “Wake Get Orders” is executed in every scenario before its output is used. Adding conditional checks within your code can help prevent errors when a node’s output is missing or its execution status is false.

By following these steps, you should be able to pinpoint whether the issue is with the workflow’s execution order, conditional paths, or the way data is being processed in batches, and then adjust the workflow accordingly.

If you continue to experience issues, feel free to share additional details about the workflow structure for further troubleshooting. Happy automating!