AutoSys FileWatcher job not running to SUCCESS even though the file is present
search cancel

AutoSys FileWatcher job not running to SUCCESS even though the file is present

book

Article ID: 388121

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

A FileWatcher job appears to be stuck in RUNNING status.  The watch_file is present and stable and the job owner has access to the file and all the directories in the watch_file path.

Resolution

Filewatchers / Filetriggers will NOT go to SUCCESS / see a file is stable until the timestamp on the file is current or older that the current system time.  Meaning, if the file has a time stamp of today and 18:00 but the FW job starts today at 12:00 it will NOT complete until AFTER 18:00.

This situation can occur if the watch_file was generated/created on a different host.  One which has a different current time / timezone than the host the file is copied to.