The file is probably found second time before the first job instance is not yet started or complete. As result you get 2 job instances in the queue and both execute email notification action on startup.
But the second job instance does not really run as the file is already moved or deleted so it sends an email and then quits. One of new enhancements in version 3.4, which will be available in a week or two, is automatic prevention of such cases. The scheduler will not start secondary job instances for the same files if the first job instance is still queued or running. : Hello
: I have a job that looks for a semaphore every minute.
: When it finds it it runs a database procedure then emails me.
: I seem to be getting the email twice which indicates that maybe the job has
: run twice.
: But when I look at the job log it only looks like it has run once !
: I have not changed the code and the only thing we have done recently is
: upgrade to the latest version of 24x7.
: I have increased the interval for it to look for the semaphore to 10 mins
: instead of 1 minute in case that has an effect.
|
