Share via

Delay in Microsoft hosted Azure pipelines

Peko 0 Reputation points
2025-05-30T05:10:05.36+00:00

Since yesterday, When i am merging the changes to the target branch, the pipelines are getting triggered after 15 mins which results in delay in the deployment.

Is it an issue from the Microsoft side?

Azure DevOps
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Durga Reshma Malthi 4,530 Reputation points Microsoft External Staff Moderator
    2025-05-30T08:33:13.67+00:00

    Hi Peko

    A 15-minute delay in pipeline triggers after merging changes could be due to several reasons. This could be due to temporary issues on Microsoft's side, such as queue congestion or service slowdowns.

    Check Azure DevOps Status to see if there are any ongoing incidents affecting pipeline execution.

    Ensure there's no new delay configured in your pipeline triggers.

    If you're using a Microsoft-hosted agent, your job might be waiting in the queue due to high demand. If the delay is in "Waiting for an agent", it's likely a resource issue on Microsoft’s side.

    Hope this helps!

    Please Let me know if you have any queries.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.