Currently there is a single global value for how long to keep a job in the queue after completion, and what to do with it after its done.
Could this have a per job override? We do a lot of different type of jobs, some are just simply processing jobs that could be deleted after a couple hours, but some need to be archived and only after 2-3 weeks etc.
Currently the single setting makes managing our jobs very hard, as we need to keep manually deleting the processing jobs (there are tens of thousands of them within a week).
Logged as a feature request.
Thanks!
Ryan
Hi Ryan,
Do you think this would fit into 6.2? Its becoming a real effort to manage the buildup of complete jobs that are simply left there because we need to keep max jobs longer (and thus have to keep every job longer)…
And the processing jobs we have set to delete right after completion as the only alternative are sometimes missing sorely - where bad render behavior is reported, but the job is missing now and we cant debug it any more.
Hey Laszlo,
We currently have this feature targeting 7.0 because it requires some core changes. The roadmap for 6.2 is basically for very minor features and plugin/script improvements (including new software support).
Cheers,
Ryan
Whats your roadmap for 7.0? Seems so distant 
We don’t have specifics, but ideally we’d like to start beta testing 7.0 in a few months. We’ll be developing 6.2 and 7.0 in parallel, which is why we’re just focusing on bug fixes and minor improvements in 6.2.
Cheers,
Ryan