Progress would like to implement conditional execution logic in their Harness pipelines based on the type of failure encountered during execution — specifically, whether the failure was user-initiated or system-triggered.

Currently, this information is only accessible through the execution-graph API, which makes it difficult to use directly within pipeline expressions or conditional steps.

Requested Enhancement:

Expose the failureType (e.g., USER, APPLICATION, SYSTEM, etc.) as a runtime-resolvable Harness variable, so it can be used directly in pipeline-level or step-level conditional execution expressions.