`Merge` node makes previous nodes executed `Not` as expected

Hi @helayzhang, welcome to the community!

The Merge node can indeed force previous nodes to run even if they wouldn’t normally do so. This is expected and explained here for example (and there are also a number of other posts of folks caught off guard by this).

To avoid such trouble with the Merge node you might want to consider building sequential flows like suggested here instead.