Dynamics Lifecycle Services (LCS) Asset Deployment - Failing with This job was abandoned. We have detected that logs from the agent may have not finished uploading.

(0) Share

Report

Posted on by markmj

584

Hi All

Using F&O 10.0.0.23

Since last week all my pipelines are failing when deploying assets to UAT. I have timeout of 0 (infinite), but the deploy step keeps failing with this error

"This job was abandoned. We have detected that logs from the agent may have not finished uploading."

We haven't changed anything and target is cloud sandbox

The upload to LCS works, the deployment says it's failed, but has actually succeeded.

Anyone else seeing this?

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

Joris dG 17,780 on at

Like (0)

Report
Copy link

Link copied!

You cannot set the time to infinite if you're using hosted agents on the free version of AZDO. There's a hard limit of 60 minutes. I'm assuming that is your issue but feel free to correct me.

Your options are to tell the deploy task to not wait to finish (so it will always succeed if it is able to start deploying). Or, you could run a private AZDO agent which can run indefinitely. I also believe there's a paid tier of AZDO pipelines that gives you more total minutes per month and more flexibility in parallel tasks and total agent runtime.

Was this reply helpful? Yes No
markmj 584 on at

Like (0)

Report
Copy link

Link copied!

[quote user="Joris dG"]
You cannot set the time to infinite if you're using hosted agents on the free version of AZDO. There's a hard limit of 60 minutes. I'm assuming that is your issue but feel free to correct me.

Your options are to tell the deploy task to not wait to finish (so it will always succeed if it is able to start deploying). Or, you could run a private AZDO agent which can run indefinitely. I also believe there's a paid tier of AZDO pipelines that gives you more total minutes per month and more flexibility in parallel tasks and total agent runtime.
[/quote]
Thanks Joris

Ran the pipeline last night and the deploy step failed after 1h 11m 56s, Job has been running for 1h 14m 55s, so it doesn't sound like the 60 minute hard limit

Best

mark

Was this reply helpful? Yes No
markmj 584 on at

Like (0)

Report
Copy link

Link copied!

Seems to have fixed itself. We didn't change a thing. last releases have worked

Was this reply helpful? Yes No