Build stuck for longer hours

tarun k 635 Reputation points
2025-06-13T05:53:45.7066667+00:00

Job running on machine is taking more than 60 minutes

We are seeing this message in one of the task

Azure DevOps
0 comments No comments

Answer accepted by question author
Durga Reshma Malthi 11,375 Reputation points Microsoft External Staff Moderator
2025-06-13T08:33:22.1+00:00

Hi tarun k

In Azure DevOps, individual steps or jobs can have a timeoutInMinutes setting. If that’s set too low e.g. 60 minutes, the job will be terminated once it hits that limit, even if it's still running.

You can increase it like this in your YAML pipeline:

jobs:
  - job: BuildJob
    timeoutInMinutes: 120
    steps:
      # your steps here

Review the steps in your build process to see if there are any that can be optimized. For example, reducing unnecessary steps, breaking up the build into smaller pieces, or optimizing test cases can help.

If you’re running on a build agent (e.g., an Azure VM, AWS EC2, Jenkins agent), check the logs and health of the agent itself. Sometimes, agent misconfigurations or resource exhaustion can slow down builds.

If possible, can you share more about what specifically the task is doing.

Hope this helps!

Please Let me know if you have any queries.

Was this answer helpful?


0 additional answers

Sort by: Most helpful

Your answer

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