Ask / Scope

When a pipeline execution is aborted, users currently need more clarity on why the abort happened. The ask is to show detailed abort information directly in the pipeline execution view.

The scope includes displaying:

The exact reason the pipeline was aborted

Whether the abort was triggered by OPA policy, pipeline logic, user action, system failure, timeout, or dependency failure

The policy, gate, stage, or step that caused the abort

Any relevant error message or decision output

Timestamp of the abort event

Recommended next action, where applicable

Link or reference to related logs or policy evaluation details

The goal is to make the abort status self-explanatory without requiring users to manually search through logs or contact platform/support teams.

Affected users

Primary users are developers, DevOps engineers, SREs, release managers, and platform support teams who monitor and troubleshoot pipeline executions.

Security and governance teams may also be affected when aborts are caused by OPA policies or gating decisions.

Impact

This reduces time spent troubleshooting aborted pipelines. Users can quickly understand whether the abort was expected, policy-driven, manual, or caused by a technical failure.

It improves transparency in pipeline execution, reduces support tickets, and helps teams take faster corrective action. For policy-driven aborts, it also improves trust in OPA decisions by showing clear reasons instead of a generic abort status.