Developer Notes

Based on our current implementation we scan for all valid transitions (up to a limit) before triggering events


Licensee has called out a strange order of execution when a state machine begins a transition to another state.

  1. The condition for the transition A -> B is evaluated as true
  2. The condition for the transition B -> C is evaluated (!!!)
  3. The Left State Event for A is called
  4. The Entered State Event for B is called
  5. The Start Transition Event for A -> B is called

Have Comments or More Details?

There's no existing public thread on this issue, so head over toAnswerHub just mention UE-15547 in the post.

Login to Vote

By Design
Affects Versions4.7.64.8
CreatedMay 13, 2015
ResolvedSep 2, 2015
UpdatedMay 18, 2020