File Watcher job Chase issues

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - System Agent (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent
• CA Workload Automation AE

Issue/Introduction

FileWatcher jobs go to STARTING and remain there. 

Chase is run and reports they are not running but then later both a RUNNING and SUCCESS event come back at the same time.

 

Environment

Release : 11.4

Component : CA Workload Automation System Agent

Resolution

See:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/11-5/release-notes.html#concept.dita_bd89790266bbc0a2aa13e33f3a0e96944a4bf911_id-.ReleaseNotesv11.5-ResolvedIssues
SYSAGT-323 File Watcher jobs do not go to running state on Unix
File watcher jobs may not have gone to RUNNING state, even though they were successfully monitoring and detecting file creation. Only occurred on Unix/Linux when the full path of the file(s) being watched were greater than 114 characters in length.