Oh yeah the screen shot bugged. This is my solution on screenshot.
In fact if for some reason you call EndAction(true) -> EndAction(null) during the same “frame” the behaviour will not be the same as EndAction(null) -> EndAction(true). In the first case, the latch will be called after, and in my situation the action will be skipped (because of the latch) for the next time I call it.
In my case I was executing action in parallel on a subFSM and stopping them outside of NodeCanvas (in a callback), and the behaviour was all wrong with entering/exiting the subFSM.