We have an application that has several file watcher jobs that do not go to success when the file arrives.
Agent operating system: Windows 2012
Agent version 11.4 build 1609
Job Definition example:
insert_job: 123_fw job_type: FW
owner: [email protected]
Release : 11.4
Component : CA Workload Automation AE (AutoSys)
The job owner lacked permissions to the directory where the file was located. While a lack of permissions like that will cause a command job to fail it does not cause filewatchers or filetriggers to fail. They will continue to run and just report permission issues in the job logs until they can successfully see the file or the job is killed.
The messages in the logs may look something like:
Error scanning \\zfsgalaxy\prod\data\Galaxy.20200602.csv: 5 (Access is denied.)