Today I needed to resubmit a bunch of jobs because of some network maintenance that caused strangeness with them and they sat “queued” until resubmitted. I wanted to resubmit them as suspended so I could complete the beginning frames manuallly before kicking them off. However, the jobs were not submitted as suspended, they immediately began rendering before I had to suspend them myself.
It sounds like perhaps there was some corruption with these job objects in the database. Can you submit a new job, and then resubmit it from the Monitor and enable the option to submit as suspended to see if that works properly? It appears to be working fine on our end, and if this test works for you as expected, we can probably assume there was some corruption and then keep an eye on it to see if it pops up again.
Cheers,
Ryan
I just tried resubmitting a healthy new job, and clicked to suspend job on submission, but it still entered the queue and immediately started to render. I tried it 3 times on 3 different types of healthy jobs, same result.
Deadline v6.2.0.24 R (cf93b1aad)
That’s so strange… I just tried resubmitting a queued job, a complete job, a failed job, a suspended job, and a pending job, and all were submitted in the suspended state. Can you check the Console window in the Monitor to see if there are any error messages?
Just to confirm, you are resubmitting by right-clicking on the job in the Monitor and selecting Resubmit Job right? I just want to make sure you aren’t resubmitting in a different way (like through a submission script).
Thanks!
Ryan
I will do more tests today. But yes, I’m resubmitting the jobs via “resubmit job” in the right-click menu in the Monitor.
I can confirm that resubmitting by right-clicking on the job, selecting Resubmit Job, and checking the “Suspend Job On Submission” box still resubmits Queued. Using Deadline Version: 6.2.0.24 R.
Yep, this has been the case every time I’ve tried, on every job. Strange that you guys don’t see it. Are we the only ones getting this?
Also, there’s no errors being produced in the console.
Are the jobs you are resubmitting dependent on other jobs that are already complete? Or maybe they have script dependencies that all pass?
I took a look at the code, and if a job has dependencies, it will be placed in the pending state, even if you ask for the job to be suspended on submission. If all of those dependencies are complete, then the job will get released shortly after submission. To confirm if this is the case, you can check the resubmitted job’s history by right-clicking on it and selecting View Job History. If the job was released because of its dependencies, it should say so.
This specific problem is easily fixable. I just want to make sure it’s the same problem you’re seeing.
Thanks!
Ryan
I have no idea what’s going on, but today it is working as expected. The resubmissions are all going into a suspended or pending state. I usually blame this sort of thing on the server room Gnomes that walk around deleting files and unplugging cables while everybody is sleeping…