# IF node misbehaving in specific cases

**URL:** <https://community.n8n.io/t/if-node-misbehaving-in-specific-cases/9801>\
**Category:** Questions\
**Tags:** node\
**Created:** [December 9, 2021, 3:04pm UTC](https://community.n8n.io/t/if-node-misbehaving-in-specific-cases/9801 "2021-12-09T15:04:19Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\
**Post date:** [December 16, 2021, 2:58pm UTC](https://community.n8n.io/t/if-node-misbehaving-in-specific-cases/9801/6 "2021-12-16T14:58:25Z")

</div>

Hi @TheFSilver, sorry for the late reply - I am afraid that’s not currently possible as confirmed here (you might want to vote on this feature request to make your voice count when it comes to changing this though):

> [@Merge node suggestion: add option to disable triggering of previous nodes](http://community.n8n.io/t/merge-node-suggestion-add-option-to-disable-triggering-of-previous-nodes/9931/2):
>
> Totally agree about the documentation. However one short question regarding your use case. Would you really need a Merge-Node in this case? It sounds to me right now like in this case simply removing the Merge-Node and rather connecting directly to the node afterward is what you want and need.

However, as suggested in this feature request, would you need the merge node in your case? In many cases you can consider directly connecting to the node afterwards.

---

_[View the full topic](https://community.n8n.io/t/if-node-misbehaving-in-specific-cases/9801)._