Hi there!
Just wanted to ask because I don’t find anything in the docs about it:
Is my conclusion correct that deleting an active job doesn’t ‘kill’/suspend the actual rendering tasks? I think I observed tasks running for a longer time after deleting an active job. To instantly get rid of an active job, I first have to suspend it and then delete it, right?
Is this on purpose? Most often I delete active jobs if something is going wrong with them or if I need to adjust something in my Nuke script etc. So in 99% of the time, keeping the tasks running for a deleted job is just a waste of rendering time.
Would be cool if there at least would be a checkbox in the deletion confirmation dialog to suspend running tasks automatically when deleting a job.
BTW: how would I be able to stop running tasks on machines AFTER I deleted a job already? Only way I see at the moment is ‘manually’ restart the slave without waiting for task completion on the machines that are still running tasks of this job. Any other way?
Hello,
I did some testing on Deadline 8.0.1, and when I deleted the job, the slave output the following:
Scheduler Thread - Task “4_41-50” could not be found because job with ID 5751f196358bec85882d35a8 does not exist
This is followed by the task cancelling and the slave moving on. Are you seeing something different? To answer your other question, the task if it’s not in the slave list anymore, you can tell the slave to cancel the current task, but again, the slave should cancel the task the moment it is deleted.
seems like you are right. Maybe it was just a result of the monitor update period etc. that I got the feeling that deleting a job keeps the tasks rendering. Forget about it for the moment, I’ll investigate that further if I can replicate it or if I’m just wrong 
What’s your network performance settings look like?
docs.thinkboxsoftware.com/produc … mance.html
Have you tuned your farm for your size? See the “Auto-Adjust” button above and simply type in the number of machines you have for optimal setup.