I'm experiencing that the end activity of a certain sub-process is always null, resulting in the default transition being taken out from the sub-process. I expected that the end activity of the sub-process would govern which transition is taken, like in the documentation and the other sub-processes of my process. A minimal example unit test that reproduces this problem is attached (reproduced with trunk/r6170). Is this a bug, or is my JPDL unsupported? If so, is there another way I can achieve the same flow? That is, having two end points after a fork, one where some and not all activities are joined and one where the remaining activities end.