Set node missing data. Works fine when running manually

Describe the problem/error/question

I have a multi-step data processing sequence, processing data received from a REST API.

When running the whole workflow at once, the Set Node does not output all of the field values that it is supposed to set (even though in history, these very fields that are skipped, show the relevent data in green).
When running the workflow manually/step-by-step, the Set Node works fine.
From my troubleshooting, it seems the issue is related to the Item Lists node earlier in the sequence
(in combination with the fact that the option for 'Keep Missing And Null Values" is true, and this branch of the processing is specifically dedicated to where there is a case of a Missing Value).

I’ve seen in the forums, and had to work around in other cases, issues related to either IF nodes and Set nodes, or Code nodes with Set nodes. From what I’ve seen, in those cases, they sometimes work when running the full execution, but present trouble when running manually. Here it is just the opposite.

(Identifying data has been changed for privacy considerations.)

What is the error message (if any)?

No error message. A silent killer.

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Output when running full execution:






Output when running manually:




"ship_to_address":"91 wallace dr brooksville, fl 34601",

"receiver_name":"bridget home services",

"supplier_email":"[email protected]",

"ship_to_name":"bridget home services",

"line_item":"reroute down spouts away from foundation, patch hole in siding, paint facia board white approx 3', remove debris away from siding"



Information on your n8n setup

  • n8n version: 0.233.1
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm via pm2
  • Operating system: windows server 2012

Hi @diskin :wave:

0.233.1 is an older version of n8n, and we’ve made a number of updates to nodes in that time. Can you try updating to the latest version (1.9.3), recreating your workflow to ensure you have the latest node versions, and seeing if this still happens?

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