When using the resume-job option on jobs with dependencies that get suspended - deadline does not put the tasks back in pending state. You need to use the mark job as pending option. Which means you have to conciously remember to use that option instead of ‘resume jobs’, but only for jobs with dependencies. We thought of maybe hiding the ‘resume job’ option completely, to avoid artist mistakes where the tasks are not being manually put back into pending state. But hiding that will make it impossible to resume jobs withOUT dependencies.
I see no reason or simple use case where a job that had pending tasks and got resumed should be immediately be put into queued state during a resume operation, instead of back to a pending state from where it came. Could the resume-job option be tweaked to properly reset the job/tasks to a pending state in case the job had pending tasks (or other dependencies)?