We tried to use the file trigger to copy the file however the file is created over a period of 60 minutes.
This file is created by a SQL job. The SQL job keeps appending to the file over a period of 60 minutes or longer.
I tried every combination of settings in the File Trigger, but because this file is created over time and sometimes a delay of up to 10 minutes between writes it's just not reliable.
Because of this we just schedule the job to start later in the day when we know the file is complete.
This all works well unless we don't receive a file that day.
The schedule will kick off the job but result in failure due to the missing file.
Currently I have a condition set that looks for the file before running the copy task.
The problem with is that we have to run the job to check for the file and if no file is present the job still runs displaying the last run date.
We would like it set so either the job does not run at all when no file is present or have the output display the message "No File to Process"