@Retired_mod We have observed that even if none of the concurrent jobs are running the single job in queued status is only picked up for run even if rest 9 slots are free.

The databricks cluster has sufficient resources to handle the concurrency thats why in initial run all 10 got executed in parallel. But after that the jobs seems to be executed in sequential manner as only single job running with rest of the slots for concurrency still available.