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.
For Each Workflow’s status remains in ‘Ready for start’ status in parent Workflow
Article ID: 88055
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
When monitoring a standard JOBP with a For Each (FE) JOBP inside of it, the FE Workflow's status is not updated. It remains in a 'Ready for start' status.
N/A
When monitoring a standard JOBP with a For Each (FE) JOBP inside of it, the FE Workflow's status is not updated. It remains in a 'Ready for start' status.
Cause
Cause type:
Defect
Root Cause: A "FOR EACH" workflow within a parent workflow shows the wrong state READY_FOR_RUN although it was already ACTIVE.
Defect
Root Cause: A "FOR EACH" workflow within a parent workflow shows the wrong state READY_FOR_RUN although it was already ACTIVE.
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 11.2.2 - Available
Automation Engine 11.1.3 - Available
Fix Status: Released
Fix Version(s):
Automation Engine 11.2.2 - Available
Automation Engine 11.1.3 - Available
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
