This content has been marked as final. Show 2 replies
There is a semantic difference when you stop a job or when you stop a specific execution of the job. User can stop a job from job activity page stop button or using "Stop Job" button on job results page. User can stop a execution by using "stop" button after selecting a job execution in specific job results page.
In former case job engine would stop the whole job and job will not be scheduled in future. However when you stop a specific execution of job, then job engine consider it as user is intending to stop only the current execution of the job so future run of job will continue to work as is.
I agree from end user perspective - the message on the confirmation screen is not very clear and we will file a bug and fix in next scheduled version of Enterprise manager.
Thanks, I was suspecting that this is what I did without noticing it. In the past I had properly just stopped the current execution of the job, but I must have been at a different screen and stopped the run. In the end I had to delete the run and schedule another run of the job from the library. Everything going well so far.
I'll have to be more careful in the future. Thanks again.