Hello,
I’ve attached an image illustrating what’s going on. It looks like the the job isn’t getting registered as being completed even though all its tasks are finished. Here’s the relevant information.
Thanks!
-Shem
This also appears to be happening on 3ds max jobs as well.
Looks like a similar problem to this:
viewtopic.php?f=86&t=10761
We have it logged as a bug, and will try to figure this one out before 6.1 is released.
Cheers,
Great, thanks!
By the way, will rolling back to an older beta theoretically fix this problem?
I don’t think it will. Because the task collection and the job object are updated separately, there is the potential for the job object to “miss” its update due to a network issue or other error. How often do you see this problem come up? If you’re seeing it a few times a day, there might be another problem we’re not aware of here…
This past week and a half or so we’ve been seeing it at least once or twice a day…
Do you know if the jobs that are being affected by this bug had Pre/Post Job scripts that were then removed prior to the Job’s completion? I found and fixed a bug that could lead to this issue, but the only way I could get it to happen was by submitting a job with pre/post Job scripts, then removing them. Was that the case with your jobs, or do I need to keep bug-hunting? 
We tend to have pre/post job scripts, but never remove them, yet also see this behavior
I looked through the current monitor to see if jobs that have this behavior all have pre/post job scripts, but thats not the case. Found 2 nuke jobs marked ‘queued’ but all tasks are complete. No scripts attached to the job (and there havent been any)
