Weird behaviour of the IF node

Took me a while to figure out.
This workflow below has 2 paths with 1 difference. The Set(that is unique to the path) has a field specified or not.
When running manually it is running as you expect but when running the workflow as a whole it doesn’t. Not sure if it has something to do with my browser or whatever. But I find it very odd.

The top path shows something that is odd:

The first object in data is clearly an empty object. but according to the IF node it is not. When this is ran manually it does show in the true branch.

The bottom path shows it as you would expect. Also the same for manual and full workflow trigger.

I have no idea what should be the cause of it. the only difference is the following set node
top path:

bottom path:

Information on your n8n setup

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

Hey @BramKn,

I am fairly sure we have an internal ticket opened for this sort of thing, I think it has something to do with the changing of datatypes between nodes.

I will see if I can dig out the ticket to link this to it.

1 Like

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