Wrong status sent to manager for File Watcher job on Windows - Lost Control

Products

• Workload Automation Agent

Issue/Introduction

If a File Watcher job is completed while the Agent is down, When agent is restarted, it will return FAIL status to Autosys even if the job was completed with success.

02/26/2023 05:03:13.963-0500 2 TCP/IP Controller Plugin.Transmitter pool thread <Regular:2>.CybTargetHandlerChannel.call[:782] - Message has been sent: 20230226 05031387+0500 ACE_XXX WA_AGENT 1234.1234_1/WAAE_WF0.1/MAIN STATE FAILED Cmpc(1) SetEnd Status(Lost control)  User(WA_AGENT) Host(examplehost)

Environment

Release : 12.0

Cause

The problem is due to Windows API limitations.

Resolution

"Since day 1 of Windows Agent filewatcher implementation, it requires Windows Agent to be alive when the file watcher reaches a completion state. This is due to Windows API limitations."

Ensure the FW job either completes or is terminated BEFORE the agent is shut down.

If the FW job continues to run when agent is shutdown and the file is found during the downtime, it can result in "Lost Control" error; which in turn "wrong status" is sent to manager as a failure event.

=-=-=-=-=-=-=-=-=-=