If the number of jobs exceeds the "max_jobs" value, the workflow is not killed
Current situation
If the number of jobs in a workflow exceeds the max_jobs in the arranger configuration, an error message appears in the logs, the workflow stops all activity but is not killed and keeps running.
Expected correction
We should kill the workflow, if the number of jobs is superior to the max_jobs value.
Edited by Martin Lafaix