We recently added support for running concurrent jobs, and you can enable this feature in the UI by navigating to the workflow form and checking the “Enable Concurrent Jobs” checkbox and click Save.
All Job Templates used in a Workflow Job Templates must have the check box “Enable Concurrent Jobs” checked.
For example, if you have a Workflow Job Template with 3 of the same Job Templates and “Enable Concurrent Jobs” is NOT checked, they will, effectively, be executed serial (one at a time). If you, however, check the “Enable Concurrent Jobs” for the single Job Template, then they will be capable of running in parallel. Note that the jobs MAY not run at the same time due to system capacity constraints.
Thanks for you response. Just to clarify, my Workflow Template is running different Job Templates. So, from my understanding, the concurrent jobs is not necessary because I am not running the same job. However, I tried to check the “Enable Concurrent Jobs” in my workflow template and after save, the option is unchecked again automatically.
I am running only 2 job templates over 4 hosts, I think that there is no issues with my server specs. 8GB RAM, 4 CPUs.
I saw, if I leave the “forks” to default in my job templates, the jobs are executed one by one in the workflow template. If I set the forks to 1 in all my job templates and I execute the workflow template, it seems to be parallelized.
Hmm, this might be a UI bug. You can observe the actual state of the field in the API. You can also change the state of what we call “allow_simultaneous” on the workflow job template via the API. I’ve attached a gif of how this can be done. Let me know if this works for you!