Two admins scan at the same time and even if both of them are deploying two different items -

• Admin A - Automation 1
• Admin B - Automation 2
• Admin C - Custom field

If any of deployments determines a dependency(ies) during review deployment of respective deployments, other deployment(s) may or may not be made aware about it/them.

Deployments should be sequential.

Also, currently during deployment action there is no locking mechanism for the deployment action.

Suggestion to implement locking the deployment items for the other admins to know items are being deployed, just like a typical version control. In this case, it would ensure integrity and consistency across deployments.