Hi,

I've been puzzling over this for a little while now and can't quite figure it out. I have a couple of jobs running on different machines. They both run nightly to kill a selection of processes but one kills them locally using the "Kill" task where the other kills processes on other machines using the "Remote Kill" task. I want tasks in both jobs to return a success code regardless of whether they find any processes to kill or not, but the local kill doesn't do this.

Remote kill just populates the StdOut with "No process found" and the task result with "Success", but local kill populates the *Result* with "Found no process to kill with the specified name on job:".

I really don't care if there aren't any processes found - I'm trying to kill them after all! So why doesn't local kill behave like the remote kill?

Thanks!

--
J

Normally, we would have a handling for this in "On error" tab. There does not seem to exist. I suggest you ignore all errors for now and we will add handling for this error type for next version.

---

I am ignoring all errors ("Only selected errors" is selected on the "On Error" tab and I've unchecked both error types), unfortunately the local kill still shows the task as having failed and this still causes the job itself to fail.

Can't you make the local kill task behave the same as the remote kill?

Please download this attached version and find the new error handling on the on error tab.

---

That seems to work perfectly, thanks 🙂

Hi again, I'm afraid I have to add to this issue - occasionally the process will exit before Visual Cron manages to kill it, eliciting an error like "Exception in Task: Cannot process request because the process (1234) has exited.". This error also goes into the result of the task and causes the job to fail.

Is there any way we can ignore this case as well? (obviously if I'm trying to kill the process and it exits first, that's not an error I care about).

Thanks.