If there is more that 1 subtask on a parent, and if the subtask updates the parent's state while traversing the subtask workflow, only the oldest substask will update the parent state as it goes through the workflow. Moving a new subtask through the workflow will not update the parent status, even though that newer subtask is executing all the same transition code.
In my business rules, having only one subtask per parent makes sense and prevents the problem I mentioned above.
Anyone have any thoughts?
Steve