Workflow tasks can now be broken down into subtasks: new optional subtasks and required fields on flow template tasks, together with an optional trigger_mode of automatic or manual — accepted on POST /v2/flows/templates and PUT /v2/flows/templates/{flowId} and returned wherever flow templates are read
Journey tasks can now require the journey to be submitted before the task completes, through a new optional journey.journey_submission_required field — available on the regular, ECP, and installer journey configuration of a task, accepted on POST/PUT /v1/workflows/definitions and POST/PUT /v2/flows/templates, and returned wherever workflow definitions and flow templates are read
New optional on_failure field added to flow template tasks, controlling what happens when a task fails