If node is KO?

Hello n8n community,

I’m experiencing an issue with the IF node in one of my workflows: it doesn’t seem to follow the defined conditions accurately, or at least it behaves unexpectedly in some cases.

Even when both conditions in an “AND” block are clearly met (e.g., hour > 7 and hour < 18), the node sometimes returns a false negative, as if one of the conditions had failed.

I’ve tested multiple configurations (boolean, string, number, etc.) and double-checked data types, but the behavior remains inconsistent.

Has anyone encountered this type of issue before? Is this a known bug, or could it be a misconfiguration on my end? Any insight would be appreciated.

Try $now.hour

This uses the luxon functions and works better in my experience

1 Like

it’s working thanks !

1 Like

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