search cancel

Unix Job stuck in "Active" instead of "Lost"

book

Article ID: 189721

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

A Unix Job in Automic Workload Automation is stuck in “Active” status forever instead of ENDED_LOST after the server the agent resides on is restarted

Example Scenario:

1. Unix job is currently running 
2. Shutdown the server where the agent is installed (Abnormal end of the Agent and the Job)
3. Restart server and restart the agent

Expected result: Unix job goes into “ENDED_LOST” status

Actual results: Unix jobs is stuck in 'Active' Status

Workaround: Restart the Agent a 2nd time, then the job will get “ENDED_LOST”.

Cause

This is caused by a defect in the Automation Engine component.

Environment

Release : 12.1, 12.2, 12.3

Component : AUTOMATION ENGINE

Resolution

Update to one of the following versions of Automation Engine or higher:

Automation.Engine 12.1.8 - Available

Automation Engine 12.2.6 - Available

Automation Engine 12.3.3 - Available