Symptoms
If a File Trigger encounters an error condition (such as a permission error) while scanning for files to trigger the job, that error is not communicated to users through the Console. As a result the trigger never starts the job, but there is no indication that there is a configuration problem with the trigger.
Workaround
If a File Trigger is not triggering as expected, more information can often be found in the adTempus server diagnostic log. For example, if a permission error occurs while scanning for files, the log will contain information similar to the following:
2014-08-06 13:44:17,869 [9] WARN ArcanaDevelopment.adTempus.Server.FileHandlers.LocalFileHandler [(null)] - Find failed System.UnauthorizedAccessException: Access to the path 'c:\test\trigger\restricted' is denied.
