Events that are started as a child of a schedule show the wrong state if the event changes its status from WAITING_HOST to ACTIVE.Schedule the monitor will still show it as WAITING_HOST.

book

Article ID: 87585

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
N/A

Events that are started as a child of a schedule show the wrong state if the event changes its status from WAITING_HOST to ACTIVE.Schedule the monitor will still show it as WAITING_HOST.
 
The status of the task within the Monitor view of a schedule doesn’t appear to update showing when an Agent goes down and comes back up.
 
Steps to Reproduce:
  1. Create a JSCH
  2. Add a file event to the JSCH and set the time to start a few minutes into the future so that you have time to disable the Agent.
  3. Execute
  4. Go to the SMgr Dialog and disable the Agent (such as the Windows Agent for example)
  5. Open the Schedule Monitor and you will see the status for the file event change to ‘Waiting for host’
  6. Go back to SMgr Dialog and enable the Agent
  7. Click refresh on the Schedule Monitor
 
Resultant Behavior: The Monitor view of the file event’s status continues to stay as ‘Waiting for host’.  Only changes to “ENDED_OK – ended normally” after the conditions of the file event has been satisfied.
 

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):
Version 11.2.2 of Automation Engine - already available
Version 11.1.3 of Automation Engine - already available
Version 10.0.8 of Automation Engine - already available

Additional Information

Workaround :
N/A