The adTempus file trigger scans for changes to watched files every 5 to 10 seconds. When it detects a change to the trigger file(s) for a job, it executes the job only once, regardless of how many trigger files have changed. The original intent was that adTempus would simply let the scheduled application know that changes had occurred and leave it to the application to scan the directory for all files to process if appropriate.

We have added an option to have adTempus trigger a separate instance of the job for each file that matches the trigger criteria (adTempus can run your application once for each trigger file). This new option will be available in version 2.1, which should be out in a public beta soon. If you are interested in obtaining a hotfix with that change sooner, please submit a support request and we can get you set up.