Set Node Fails When Triggered, But Succeeds When Run Manually

Questions
, , ,
1

Set Node Fails When Triggered, But Succeeds When Run Manually

Describe the problem/error/question

I am having a similar issue to the one raised in this (now closed) question from 2023 Workflows fail when triggered, but succeed when run manually . When I try to trigger a ‘set’ node as part of a larger workflow it does not work, however when I trigger it manually it works. The main issue is that when using a trigger one of the columns pulls in as null (screenshot below), which does not happen if I go back and click ‘Execute Step’ manually.

Screenshot 2025-10-10 at 10.53.51 AM
Screenshot 2025-10-10 at 10.53.51 AM1920×953 125 KB

Please share your workflow

Tried to paste my workflow but it's pretty massive and caused a crash! Attaching a screenshot with some of the nodes that are giving issue circled. This happens for 5 'set' nodes total, but only 3 fit in the screenshot. The 5 are all basically the same thing, just connected to the same data source with different filters.

Screenshot 2025-10-17 at 11.35.55 AM
Screenshot 2025-10-17 at 11.35.55 AM2368×1305 461 KB

Information on your n8n setup

  • n8n version: 1.112.5
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Cloud I think? It’s hosted by my company and I log in through my browser
  • Operating system: MacOS Ventura 13.3.1(a)
2

Which trigger node are you using? The “null” values are returned directly from your DB from the query, right? So the input/query must be somehow different. However, it is hard to debug if I don’t see which nodes were actually executed and what the output was in each case.