Deployment task page shows incorrect "ran for" time for process with Manual Intervention step

[ryanrousseau]

Team

• [X] I've assigned a team label to this issue

Severity

UI bug

Version

Earliest tried was 2022.2 (Build 387-hotfix.903)

Latest Version

2022.2.2754

What happened?

I noticed that the deployment task log shows two different values for how long the deployment ran for when deploying a release with manual intervention step. See screenshot below. The deployment ran for a few minutes but the first set of text says it ran for 1 second.

It looks like this is relatively new. Deployments from yesterday seem to be fine.

Reproduction

• Create a deployment process with a manual intervention step and a script step with a sleep of 15seconds
• Create a release
• Deploy the release
• Approve the intervention
• Observe the task log screen shows deployment ran for 1 second whereas the deployment took much longer

Error and Stacktrace

No response

More Information

When the manual intervention step is reached while deploying the release, the TaskState gets set to "Queued" and Completed field gets populated. Duration is calculated as Completed-StartTime. The completed field should change after manual intervention is received and deployment resumes.

Workaround

No workaround as the deployment itself succeeds, just the duration reported is incorrect.

[mik-ky]

Hey @ryanrousseau,

I've tried replicating on my cloud instance but was unable to reproduce the issue:

Is this a recurring issue?

[ryanrousseau]

Hey @mik-ky - after double-checking, it seems it only impacts projects with a manual intervention step, potentially as the first step.

Given that new info, I'm not sure how long it's been happening since it only affects that subset of deployments.

[mik-ky]

Thanks @ryanrousseau.

By adding a manual intervention step, I was able to reproduce this behaviour of server task details returning a fixed duration each interval. From testing, when it runs the manual intervention step, it looks like the duration stops incrementing and stays stopped until the whole process is complete.

[donnybell]

Another affected customer [Internal Link]

[Octobob]

:tada: The fix for this issue has been released in:

Release stream	Release
2024.1	2024.1.1679
2024.2+	all releases