Deadline Version: 10.4.10 / Linux Rocky 9
Hello,
We have encountered an issue with Auto Task Timeout in Deadline that does not appear to align with the documentation, and we would like confirmation of the expected behaviour. If our understanding is correct, this may indicate a bug.
Issue Summary
According to the Deadline manual:
-
Global Auto Task Timeout Settings determine timeouts based on the render times of completed tasks.
-
Per-Job Setting: “Enable Auto Task Timeout”
The manual states that enabling this option causes the job to use the Auto Task Timeout parameters specified in the Repository Options.
However, we observe that Auto Task Timeout is being applied to jobs even when “Enable Auto Task Timeout” is NOT ticked in the job properties. This implies that the global Auto Task Timeout settings are always enforced, regardless of the job-level setting.
Expected vs. Observed Behaviour
• Expected: If the “Enable Auto Task Timeout” checkbox is not ticked for a job, the Auto Task Timeout settings from the Repository Options should not be applied to that job.
• Observed: Auto Task Timeout is still applied to the job, regardless of whether the checkbox is enabled or disabled.
Could you confirm if this is the intended behaviour? If not, this appears to be a bug. Have other users reported similar issues?
Second Issue: Interaction Between Auto Task Timeout and Minimum Task Render Time
Additionally, we would like clarification on how Auto Task Timeout interacts with the Minimum Task Render Time setting.
-
If both values are set, does one override the other?
-
Is it a boolean AND condition (both conditions must be met), or a boolean OR condition (whichever limit is reached first)?
The documentation does not explicitly state how these two settings work together.
We appreciate any insights you can provide!