The catch is that regular tracks are triggering the next item from the playlist at CUE NEXT point, but the playlist event doesn't have such a thing. So, the playing track reaches CUE NEXT, the event does what is suppose to do, but the next track waits for CUE NEXT, which doesn't exists. The playing track end and the watchdog forces the waiting track to start.
Now, there are two possible fixes for this:
1. I can add a PLAY action when the event is firing, but since the event is processed in a separate thread, for events with many actions (like loading many files), it could happen that the playlist will advance even if the event it's not completed modifying the playlist.
2. The user simply add a PLAY action at the end of each manual event and in this manner, the PLAY action will be fired at the right time.