We have very simple trigger that is monitoring a folder. The folder is empty until the file is dropped in. The job is set to look in the folder every minute and run if the file is present. The files are moved into the folder by users with proper permissions and the files are complete before they are moved into the folder. The job runs without any issues the entire week, but on Monday mornings the job wouldn't run. When we looked at the job, we found that the trigger wasn't checked.
Will the trigger disable itself after a certain number of unsuccessful attempts? That is the only thing we can think of. The trigger only has been unchecked after the weekend in which there wouldn't have been any activity. It would have looked in the folder over two thousand times without at file being present. Can this be the problem? We have multiple jobs setup like this and having to re-enable the trigger every Monday morning is becoming cumbersome.
Any insight would be greatly appreciated.

If the folder becomes unavailable due to server maintenance, reboot, etc. the job will attempt to reconnect to the network share. After the job has reached the maximum number of reconnect attempts the trigger will become "unchecked". You can set the number of reconnect attempts and the interval between each reconnect by opening up the file trigger and going to the "File" tab.

You will probably see the reason why in the log_serverXXXX.txt from Monday. The problem is probably related to that a remote server as disconnected or similar.

---