ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
ForEach Workflow does not trigger parent Workflow
Article ID: 84349
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:
However, the parent Workflow is not triggered correctly.
And stays in an active status until there is manual intervention.
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>
<Please see attached file for image>
And stays in an active status until there is manual intervention.
<Please see attached file for image>
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.
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
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
N/A
Attachments
Feedback
Yes
No
Powered by
