Hi,
we’re using custom image conversion jobs that depend on say compositing jobs. Sometimes a comp job is deleted on purpose, but it’s conversion jobs still are in the queue, because an artist forgot to kill them as well.
Is it possible in DL3 with built-in methods to have a child job automatically deleted in case it’s parent job was deleted?
Marcus
Hey Marcus,
This one is on our todo list. We’re thinking the best way to handle this is when the user goes to delete the job, they are warned if it has dependent jobs, and are given the option to delete their own dependent jobs (we wouldn’t want other user’s jobs getting deleted). Maybe a notification could be sent to the other owners so at least they are aware and can handle the situation appropriately.
Then there is the case of auto deletion. In this situation, we might just send a notification to all the owners who have dependent jobs (including the owner of the original job).
This feature hasn’t been targeted for any release yet, but it is on our radar.
Cheers,