Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Can someone help me understand how a timeout set at a task level
```@task(timeout=timedelta(hours=1))```
interacts with the node default set in the propeller / scheduler configuration?
```default-deadlines:
  node-active-deadline: 168h0m0s
  node-execution-deadline: 72h0m0s
  workflow-active-deadline: 0s```
My assumption was that a task level timeout spec would override the default we set. What we've observed is that a value under 72h in the task decorator does terminate the task but anything over 72 hours still terminates the task at 72hours with the same message:
```Last Error: USER::task execution timeout [72h0m0s] expired ```

Deadline for a node you can set it to infinity as well

Ah. This makes sense. Thanks Ketan for confirming!