After server reboot, running jobs do not fail with ENDED_LOST

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

When a server was rebooted, the jobs that were running at that time did not end with ENDED_LOST. Instead, the job ended with status ENDED_OK. It should have ended with ENDED_LOST, so it would block the workflow.

In the jobs a "cmd /c" command is used.

Environment

Release : 12.3.x

Component : Automic Workload Automation

Cause

It is because of "cmd /c" command. It carries out the command specified by the string and then terminates.

Resolution

Do not use the "cmd /c" command so when Agent is being restarted the job receives the ENDED_LOST status.