ForEach Workflow does not trigger parent Workflow

Document ID : KB000084349
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
N/A

A ForEach Workflow, which aborts during generation, does not trigger its parent Workflow.  Therefore, the parent Workflow does not continue.

Investigation

In the following example the ForEach Workflow has block and abort set:
0EMb0000001UxZY.png
 
 
However, the parent Workflow is not triggered correctly.
0EMb0000001UxNm.png

And stays in an active status until there is manual intervention.
0EMb0000001UxNr.png
Environment:
OS Version: N/A
Cause:
Cause type:
Defect
Root Cause: A ForEach workflow that aborts during generation doesn't trigger its parent workflow and therefore the parent workflow does not continue.
Resolution:
Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Automation Engine 12.0.2 - Available
Automation Engine 11.2.4 - Available
Automation Engine 11.1.6 - Available
Additional Information:
Workaround :
N/A