boundless-grass-11734
07/18/2024, 8:45 PM@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
freezing-airport-6809
freezing-airport-6809
freezing-airport-6809
boundless-grass-11734
07/22/2024, 4:10 PM