Concurrent deployments at different stages on the same pipeline

What setup is required that a second deployment will kick off and go to the first environment stage in a pipeline, when an first pre-existing deployment has moved beyond the first environment stage and is in the second or third environment?

Currently the second deployment is waiting in a queue when the first environment stage is free.

@EamonRooney

@nayam could you answer this one?

In Pega’s Deployment Manager, only one deployment per environment is supported at the same time. This is due to the fact that the Pega import process is not thread-safe. If the same rule is modified during parallel deployments, deployments could fail and it would be challenging to identify which deployment was the source of the failure. Therefore, a second deployment will not start until the first deployment has completely finished and moved beyond the first environment stage. This is to ensure consistency and minimize potential failures.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

Why can I only have one deployment per stage?