Add to my comment; we have to define "Workload Automation" and "Workflow Automation" to understand the Subject of our Talking; in Workload Automation we are dealing with the use of Resources; in Workflow Automation we are dealing with (time) dependencies between Workflow…
Besides the standard arguments, such as cost and support, my focus is a good architecture that reduces costs and helps support
The Workflow graphs should be DAG's or better nested DAG's.
ControlM, Airflow supports nested DAG's;
Redwood only supports Chains, but with Chains…