It would be great if suspending a job that had pending tasks would remember the pending tasks’ previous state. So when you resume it later, it could place those tasks right back in a ‘pending’ state, instead of all tasks being put right into ‘queued’.
Its easy to forget that a suspended job had dependencies / pending tasks, so most people just resume the jobs instead of the explicit “mark job as pending” option (marking the entire job pending is less then ideal, because then you have to wait till the pending job scan cycles through the job to clear up what was queued/pending.)
Thanks Laszlo, I’ll add that to the wishlist.
Hello,
I’m surprised this issue hasn’t been flagged more often in the last eight years. I see this as a bug/unintended side effect rather than a feature sitting on a wishlist with seemingly low priority.
It would be really helpful if this could be addressed in a timely manner.
Perhaps I’m missing something about its intended use and somebody could clarify the rationale behind the current behavior?
Thanks