What could be the main reason for our AWS metaflow environment’s AWS batch to only being able to run one job at the time - i.e. sequentially? So when I look at a the queue I only see one job running and the others are Runnable. From what I can see the provisioning model is EC2 - not sure if this is the root cause? Thanks.

you might be getting bottlenecked on compute configured within AWS Batch

Thanks. Would you know what the devops guys may need to change to fix this?

Hard to say without knowing your setup, but I would recommend looking at your compute environment configuration

Sorry about very late reply. We figured it, it was related to the (minimum?) number of CPUs in the original metaflow terraform