My release pipeline is significantly delayed after build pipeline is finished, even though continuous deployment is enabled

Hi @Eric Rook ,

Follow the below troubleshoot steps to resolve this issue:

Check the Azure DevOps status page: https://status.dev.azure.com

If there's an incident in region (especially related to Pipelines), that could explain the delay.

Continuous deployment trigger setting:

Go to your release pipeline and double-check:

• The CD trigger is enabled under the artifact section.
• There are no filters (like branch or tag filters) that might be holding it back.

Queue or deployment concurrency

Your release may be sitting in a queue if

• Another deployment is in progress for the same environment.
• The environment is configured to allow only one deployment at a time. Check under Releases > Your Pipeline > Release History and look for anything stuck in a “Queued” state.

Agent pool overload

If you're using a private or shared agent pool, it might be busy.

Check under Project Settings > Agent Pools to see if jobs are waiting due to lack of available agents.

Recent changes

Has anyone edited the pipeline recently? Check if someone:

• Added manual approvals
• Changed deployment gates
• Updated deployment conditions

Any of these can cause unexpected behavior or delays.

Try triggering a build manually and see if the release fires off right after. If not, check the release logs to see what’s holding it up.

By following these steps, you can hopefully identify the source of the delay and take appropriate action to resolve it. Let me know if you need further assistance or have any other questions.