Automatic transition

Also known as Eventless transition

Automatic transitions are transitions that are triggered as soon as a state is entered, sometimes causing the state that was just entered to exit.

Automatic transitions don’t have an associated event, as the mere being in the state implies that the transition should be taken.

Automatic transitions are usually guarded. Such a guarded automatic transition is checked immediately after the state is entered. If the condition doesn’t hold then the machine remains in the state, with this automatic transition in play for as long as the state is active. Every time the statechart handles an event, the guard condition for these automatic transitions are checked. If the guard condition ever succeeds, then the transition happens.

If there are many automatic transitions in play, they are all checked. In some statechart systems, only one guard is allowed to be true at any point in time; in others, the transitions are ordered, and the guards are checked until a one of them succeeds.


A transition arrow, but without the name of an event, only guards and/or actions.

           [ i > 4 ]


Guarded transitions can be used to cause a machine to “wait” in a certain state, until some condition holds, regardless of what else is happening in the form of events. For example, a machine could be in the ‘filling’ state until some threshold is reached, by defining an automatic transition from the ‘filling’ state with a guard contents >= capacity. Immediately after the contents reach the capacity, it would exit from this ‘filling’ state.

By using an in guard, it is possible to coordinate different parts of a parallel state. When the one region ends up on a certain state, it can wait until another region enters a specific state.

If a machine is in a state with a guarded automatic transition, then that guard is checked as often as possible. Being event driven, the guards are effectively only checked whenever an event has been processed, but also after other automatic transitions have fired, or other internal events (such as raised events are fired.

Automatic transitions can be used to implement a condition states, in other words, a state that only has automatic transitions. This is done by creating a state that only declares guarded automatic transitions, in such a way that it is guaranteed that the machine will always pick a transition upon entry, never resting in that state.


In SCXML, automatic transitions are <transition> elements that don’t have an event attribute:

<transition target="otherstate" cond="mycondition"/>


In XState, an automatic transition is called a transient transition. It is a normal transition that is hooked to the null event identified by the empty string:

on: {
  '': [
    { target: 'otherstate', cond: mycondition }