Hey,
I seem to have issue with setting auto timeout for the job. I have it enable in job settings and also inside repository settings. Yet it seems like it’s not setting the timeout for the job.
Job already rendered enough frames to calculate maximum task render time and yet it’s till set to 0: http://www.dabarti.com/screens/s4953f0b4-b371-4f7c-a75c-a211f29ef1db8.png
Job settings: http://www.dabarti.com/screens/s53d149de-5767-466c-a792-bd611d5cf990a.png
Am I doing something wrong or there is bug somewhere?
We’re currently on:
Repository Version: 10.1.8.5 (60c6a62b5)
Integration Version: 10.1.8.5 (60c6a62b5)
Best,
Tomasz
Hello!
If set to only use either ‘Minimum number of completed tasks’ or ‘Minimum percent of completed tasks’ do you see different behavior?
Something to note is that if it’s the first or second task that should get timed-out that might not happen as the auto-timeout won’t have been calculated yet.
If that’s not the case then I wonder if there’s a bug. Could you share an archive of that job? Either here or in a ticket to support.thinkboxsoftware.com if you don’t want that up for the internet to poke through.
Hey
I tried both minimum number of completed tasks and minimum percent… Nothing works.
This happens for all of the jobs.
Does it require some background service to be running?
Best,
There’s no other service needed. Could you share a Worker log from a job you’d expect to get interrupted?
