Hello Eugene, The scenario you have outlined can not happen - you’re safe from this kind of race thanks to the Actor’s properties.
The transition as well as calling the transition handlers for the new state are all still happening during Actor A’s receive, which means that it is guaranteed that the state will have changed to S2 before the next message is processed. You can track this flow by looking into FSM.scala and track the flow from receive thorough through processMsg right to makeTransition and handleTransition. If you need more tips let me know — happy hacking! -- Konrad 'ktoso' Malawski hAkker - Typesafe, Inc -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
