Your expectation is correct. The second event should be processed by the new state as described in the documentation. Of course, I may have made a mistake and you might have encountered a bug, but I’m pretty sure this case should be covered. Please try the following:
- Check that the order of the events is correct. If the second event arrives before you can fix the problem by adding the second event as a “deferred” event in the initial state
- Check the policies on the TriggerEvent (as described here)
- Enable the visual logger (described here) and set the level to “Very Verbose”, you should get a glimpse of what exactly is happening in your FSM