"QPool.Char" wrote : Is this right? But this behaviour wouldn't explain why it works with ended B, but not otherwise... Without delving into the code, it makes sense to me. If B has completed, then the associated token will have ended. Hence, when the other tokens reach the join, all the tokens are accounted for and the parent token can advance. If B is not yet complete, then the parent will end up waiting (indefinitely) for the token as, without any further tokens ending at the join, there is no trigger to release the parent token. "QPool.Char" wrote : Is there any workaround? Perhaps a custom node on one of the fork transitions can generate the task? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132071#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...