"brittm" wrote : Conceptually, it seems to me that a transition should never be taken if it has an explicit condition that is not met. Well, I'm not sure what the end-all outcome is of this discussion, however: | <decision name='decision1'> | <transition to='state1' name='path1'> | <condition expression="#{x==1}"/> | </transition> | <transition to='state2' name='path2'> | <condition expression="#{x==2}"/> | </transition> | <transition to='state3' name='path3'></transition> | </decision> | Jbpm 3.2.3: if x = 2, path2 is taken. if x = 5, path1 is taken. if x not set, path1 is taken. The last two feel incorrect to me. I can resolve this by moving the default transition (path3) to the first position, but the behavior seems incorrect by reason stated in the quoted post. So, JBPM simply is executing transactions with invalid conditions? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203294#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...