If I was to suspend jobs in que for some reason, and then select the job, and take resume. the dependencies are lost, and the job fails due to Nuke cannot find the ext file that the 3dsmax render would have been outputed.
Perhaps Iâm misunderstanding something, but you shouldnât need to suspend jobs whose dependencies are suspended, since they wonât be released to render until the dependencies have resolved.
If you do suspend the dependent jobs, instead of choosing 'Resume", you should select âMark Job As Pendingâ and youâll get their original behaviour of needing to pass a pending job scan.
You can do it on the whole batch. They should automatically requeue if their dependencies are met. I also wrote up a quick thought for the dev team internally here for future users:
Iâd like to see a dialog come up when users resume a job with unfinished dependencies that asks âThis job has unfinished dependent jobs, would you like to pend it instead?â and choosing âYesâ would pend, âNoâ would resume.
I think there may be a more creative way to inform users the result of their actions, such as renaming âresumeâ to âforce queue nowâ or something clever when a job has known dependencies.
âIâd like to see a dialog come up when users resume a job with unfinished dependencies that asks âThis job has unfinished dependent jobs, would you like to pend it instead?â and choosing âYesâ would pend, âNoâ would resume.â
would be a nice way m but would that not just fail the job if I would to choose no? The same scenario that we have? If i choose NO in you example, the jobs would go to the que, and all jobs depended on the .max render would fail?
Yup, theyâd fail. There isnât a perfect scenario here, so weâd trust that you knew what you were doing. We could add a little extra blurb like âChoosing âNoâ will ignore any existing dependenciesâ.