Hmm. This happens because the Trigger Event node is initialized before the Start Event node. This of course should not happen.
I have just properly implemented a way to always execute nodes in correct priority, thus fix this problem you are facing.
If you want I can send you the new version to your email 🙂
Should I use your registered email account for that?