ForEach Workflow does not trigger parent Workflow

book

Article ID: 84349

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

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:

<Please see attached file for image>

0EMb0000001UxZY.png
 
 
However, the parent Workflow is not triggered correctly.

<Please see attached file for image>

0EMb0000001UxNm.png

And stays in an active status until there is manual intervention.

<Please see attached file for image>

0EMb0000001UxNr.png

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.

Environment

OS Version: N/A

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

Attachments

1558704275465000084349_sktwi1f5rjvs16liz.png get_app
1558704273657000084349_sktwi1f5rjvs16liy.png get_app
1558704271614000084349_sktwi1f5rjvs16lix.png get_app