Release pipeline failed to deploy package - We stopped hearing from agent Hosted Agent

(1) Share

Report

Posted on by ThomasWilke

766

Hello community,

we are running devOps release pipelines to upload and deploy code packages through LCS into our sandbox environments. Lately we get the following error for one of the sandboxes:

We stopped hearing from agent Hosted Agent. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610

This message says the deployment failed even though LCS has deployed the code package to that environment. Has anyone an idea what can cause this issue?

I have the same question (0)

All responses (6)

Answers (1)

nunomaia 25 Moderator on at

Like (0)

Report

Pipelines have a maximum execution time. DveOps considers that lost contact with Hosted Agent after some time. Check if execution times have increased a lot.

Was this reply helpful? Yes No
Martin Dráb 237,965 Most Valuable Professional on at

Like (0)

Report

The message doesn't say that the deployment failed, just that the agent stopped communicating at some point.

Was this reply helpful? Yes No
ThomasWilke 766 on at

Like (0)

Report

The stage for our TEST is running for 1 hour and 15 minutes and fails with that message. LCS says deployment complete after an hour, so it should be done before DevOps tells me that it failed.

We deploy the same package to another SAT environment and this is always good. See screenshot below:

Was this reply helpful? Yes No
ThomasWilke 766 on at

Like (0)

Report

Just as an additional information:

what I noticed now is that deployment to UAT is always taking less than 60 minutes. TEST is taking more time to deploy. Maybe there is a timeout somewhere.

The timeout settings in that release pipeline are all set to 0 (unlimited).

Was this reply helpful? Yes No
Verified answer

nunomaia 25 Moderator on at

Like (1)

Report

If I'm not on mistake, the free tier of pipelines have a 60 minutes timeout. It's not possible to control it

Was this reply helpful? Yes No
Suggested answer

ThomasWilke 766 on at

Like (0)

Report

Thank you for the hint. It was based on free pipelines - I guess this explains why. I changed it to paid pipelines. Now it is working fine.

it would be really great if there would be a message to inform the user to switch to payed pipelines.

Was this reply helpful? Yes No