Incorrect duration task in Octopus

Hi,
I am seeing an issue where it is giving the wrong duration time for a deployment. As you can see below the deployment ran for 1 hour and 37 minutes but it displays 1 minute for the duration.

But when you look at the log it says the duration is 1 hour 37 minutes

Is this a bug?

Kind Regards,
Micheál Power

Hi @mikepower79,

Thanks for getting in touch!

The timings seem a little odd; in the first screenshot, the task start and completion times don’t seem to line up with the deployment log.
Is there any chance the deployment was run more than once?

If you can download the full task log and send that across we’ll take a look to see if we can identify the cause.

Regards,
Paul

Hi @paul.calvert,
This is the correct screenshot:

I have also attached the log.
ServerTasks-3203603.log.txt (254.1 KB)

Kind Regards,
Micheál Power

Thanks for that.

Looking through the log, it looks like it is taking the timestamp from when the manual intervention triggers and using that as the “completed” time.

I’ve run a quick test on my cloud instance, and I’m seeing the same issue occurring there, so, will raise it with our engineers to look into.

1 Like

Hi @paul.calvert,
Thanks for the feedback.

Kind Regards,
Micheál Power

Issue created: Deployment task uses timestamp of Manual Intervention for completion time. · Issue #7996 · OctopusDeploy/Issues · GitHub

1 Like