Summary
The user is seeking clarification on the interaction between a task-level timeout set with @task(timeout=timedelta(hours=1)) and the default timeouts in the propeller/scheduler settings. They believe the task-level timeout should override the default settings. However, they have noticed that when the task timeout is under 72 hours, it terminates as expected, but if it exceeds 72 hours, the task still terminates at the 72-hour mark, accompanied by an error message about the execution timeout. They mention that the node default is the maximum and that the deadline for a node can be set to infinity, which is intended to allow draining nodes.