If the job cannot delete the semaphore file it must write an error message to the job log and stop running if the job option "ignore errors" is not turned on. It may also happen that the job deletes the file and while it is running another semaphore file is created. To stop a job, simply go to the task manager and kill the process created by that job. If you let me know more details about your job design, I can help you to find a solution to this issue. : I have a bog standard job set up using filewatch.
: The job runs detached, with 'delete semaphore before run' checked.
: The job checks for the semaphore every minute. : Very occasionally the job detects the presence of the semaphore but fails to
: delete it, this results in the job running every minute. : If I look at the job queue, it still thinks the job that created the
: semaphore is running. To overcome the problem I deleted the semaphore
: manually and forced the dependant job to run, ignoring the fact that the
: semaphore does not exist. : I can't delete the job that it thinks is still running through the job queue,
: so I'll probably have to re-start the scheduler to clear it at a
: convenient time. : Any ideas? : Thanks
|
