Hi Martin, As i mentioned in the other mail, you can define startup order for top level groups/cartridges in the application and you can define startup order in the group definition for group's subgroups/cartridges. In your case, i'm not sure why are you trying with nested group definition.
Group1 (c1) should start up after group2, group2 (c2) should start up after group3 (c3) The above is a linear relationship where we can say a startup order as "group.group3, group.group2, group.group1". So that group3 will come up first. Then group2 and group3 will come up accordingly. But if you would like to test nested groups, then you can organise the groups as below: group1 --> c1, c2 where startup order is "c1,c2" group2 --> c1, c3 (no startup order means both will come up in parallel) group3 --> group2, c2 where startup order is "group2, c2" group4 --> group1, c3 where startup order is "group1, c3" application --> group3, group4, c1, c3 where startup order is "group3, c1", "group3, group4" If you write up group definition and application definition for the above mentioned relationship, you can see how these nested groups are brought up as well as you can see some groups/cartridges will be brought up in parallel as well. Thanks, Reka
