Hi,
could it be a race condition that within the sequence of PLayMaker sending this event to the list of FSM listening to that event, one of the state fires another event that make a given fsm jump to another state and miss the original event you sent?
It happens to me quite often, basically, a cascade of chain events affecting the same fsms can create this kind of trouble.
you need to cut down features, for example, all fsm listening to that event, should not do anything, disable all actions and let fsm stay on the receiving state, fire the event and check that all is sound, then add features back one by one.
Or do the opposite, take one feature out and test until you can't repro, then you narrow down the area giving trouble.
Bye,
Jean