Well I found out that "negation" on "any exists" is risky.
For example, my Tagging bots use team tagging D to mark themselves as "seeing" the team tagged A enemy (in close, mid, long) range.
So it means, that if at least one sees the enemy, there is D tag on the bot.
But there need to be situation when A have to be changed (for example, it runs away or gets killed).
Which means, that all the D tagged bots will untag themselves.
So I need to know that I need to mark another enemy A, which means I have to make condition "If there is noone D tagged ally, then tag the closest enemy to A" - meaning, if there does not exist any ally who is in proximity of current target, then change current target.
And condition "If any ally tagged D not exist" will not work, as it will light up green, if there are non D tagged allies.
So I usually do the negation of "If the closest D-Tagged ally not exist" then... It guarantees that filter will try to find out D tagged ally and because of NOT Exist, it will negate - so will be green, if actually no D tagged allies exist.
So use "If closest (your condition) enemy/ally NOT exist" form to negate these situations.
Examples "If closest fleeing from self, fleeing from ally enemy NOT exist" -> Means that there is not a single retreating enemy.
If closest enemy-attacking ally NOT exists -> Means that there is no ally shooting enemy (hopefully coz they are dead)