Please note the wording of conditions in AppSense 8.5 onward has changed to make things a bit clearer. However 8.4 and below have the wording highlighted here.
Node Groups act like any other node in most respects with a few significant exceptions;
- All nested actions within the Node Group are executed prior to any sub nodes.
As you can imagine a badly written script could very easily add delays to any nested actions.
- Only reusable nodes can be nested within a Node Group, no individual actions.
All other actions must be added as sub nodes dependent on nested actions completing.
- All conditioning nested within the node group must return a true result.
As covered in a previous post regarding scripting within EM; scripts by default will always return a true result without proper exit codes.
The condition that all conditioning within a node group must return a true result means technically the node group is working exactly as it is intended to do so. A support call to AppSense will yield the result of “working as intended”.
Reproducing the issue
In this section we will reproduce the issue in AppSense Environment Manager 8.4. Please feel free to skip this section if you would prefer to go straight to the solution below.