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.

When monitoring a standard JOBP with a Foreach JOBP inside of it - The FE Workflow does not get its status updated

book

Article ID: 88188

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
FE JOBP stays in a 'ready for start' status

When monitoring a standard workflow that contains a for-each workflow, the FE workflow stays in a status of 'ready for start' within the monitor while completing successfully.

A parent workflow shows the wrong state READY_FOR_RUN although it was already ACTIVE. 

Cause

Cause type:
Defect
Root Cause: Refer to description

Environment

Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:

Resolution

This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Automation Engine 11.2.2 - already available
Automation Engine 11.1.3 - already available
Automation Engine 10.0.8 - already available

Additional Information

Workaround :
N/A