Chris, imo it is an oversight. I can't think of a good reason. What would you think of having an .cancel() take the default transition, having and .cancel(Transition trans) or .cancel(String transName) take the one specified. The required .end(...) methods are already available. Not taking any transition is a difficult case. If this is the only task, the process would in in undefined state. If this task(node) is one of the teeth(?) of a fork, the join needs the token, so it has to take a transition for the join to work. Only if there are multiple tasks in a node this is an option. Let's leave this one out for the moment View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960528#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...