Aria Automation Orchestrator reports an incorrect, extremely large execution time (e.g., thousands of days) for a workflow element under high concurrency

Products

• VCF Automation

Issue/Introduction

A workflow element may display an implausibly large elapsed execution time in the Orchestrator UI or logs. For example, tens of thousands of days even though the overall parent workflow executed in minutes.

• This has been observed during bulk/high-concurrency operations.
• No actual delay in execution.

Environment

Aria Automation Orchestrator 8.18.1

Cause

This is a rare race condition in Orchestrator's internal workflow-statistics tracking. Under very high concurrency, a timing window can occur where an element's start time is not recorded before its elapsed run time is calculated.

Resolution

A fix will be included in a future patch release of Aria Automation Orchestrator; there is currently no available workaround.