Hmm. I tried replicating this, using a stock action task, like for example wait, which also does call “EndAction” after a certain amount of time:
[attachment file=”2017-10-06_19h37_14.png”]
With the above example, the nodes are called in the correct order and the Wait node does indeed make the tree wait before the last conversation node is called.
Is the example I made above equivalent to the problem you are facing?
If not, is there any way I can replicate the problem?