New featureMedium

AWS HealthOmics now supports task-level timeout for WDL workflows

AWS HealthOmics enables setting maximum execution duration for individual WDL tasks, allowing cost control and automated error recovery

AWS HealthOmics now supports task-level timeout for Workflow Description Language (WDL) workflows, allowing you to set maximum execution duration for individual tasks. This feature helps healthcare and life sciences customers control costs and enable automated error recovery by defining time bounds on WDL tasks. You can add the omicsTimeout runtime attribute to any task's runtime section to specify the maximum duration a task is allowed to run. When a task exceeds the specified duration, HealthOmics stops the task and sets both task and run statuses to failed. The omicsTimeout attribute accepts duration values with standard time units (such as 90s, 2h, 1d), preventing tasks from consuming unnecessary resources and helping set cost guardrails during workflow development. This capability is available in all supported AWS HealthOmics Regions: US East (N. Virginia, Ohio), US West (Oregon), Europe (Frankfurt, Ireland, London), Israel (Tel Aviv), and Asia Pacific (Seoul, Singapore, Tokyo).

Read the original AWS announcement