> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/harness-platform/use-harness-platform/pipelines/executions-and-logs/view-and-compare-pipeline-executions.md).

# View and compare pipeline executions

View and compare the compiled YAML used for pipeline executions to understand changes and troubleshoot issues.

You can view the compiled Harness pipeline YAML used for your pipeline execution and compare two executions. Comparing pipeline YAML helps you understand the changes that occurred between executions, which can help with troubleshooting.

***

## What you will learn from this topic

* How to [view pipeline execution history](#view-executions) and access logs.
* How to [view the compiled YAML](#view-compiled-yaml) for a specific pipeline execution.
* How to [compare two executions](#compare-executions) to identify changes and troubleshoot issues.

***

## Before you begin

* **Harness account access:** You need access to a Harness account with pipelines. For how to access or create a Harness account, see [Getting started with Harness Platform](/harness-platform/new-to-harness-platform/get-started.md).
* **Pipeline execution permissions:** You need **View** permission on [Pipelines](/harness-platform/use-harness-platform/platform-access-control/permissions-reference.md#pipelines) to view execution history and compiled YAML. To get this permission, an administrator must assign you a role that includes it. Go to [RBAC in Harness](/harness-platform/use-harness-platform/platform-access-control.md) to understand role-based access control and [Manage roles](/harness-platform/use-harness-platform/platform-access-control/add-manage-roles.md) to configure role assignments.
* **Familiarity with Harness concepts:** You should be familiar with [Continuous Delivery key concepts](https://developer.harness.io/docs/continuous-delivery/get-started/key-concepts) or [Continuous Integration key concepts](https://developer.harness.io/docs/continuous-integration/get-started/key-concepts).

***

## View executions

The **Executions** page lists every execution of every pipeline in a project, including reruns and child pipelines, with the 30 most recent days shown by default. Use **Search**, **My Executions**, **Status**, **Timeframe**, or **Add Filter** to narrow the list, and use the sort dropdown at the top right to change the sort order.

![](https://173309742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3F2TpHXhur2QtQnORSM9%2Fuploads%2Fgit-blob-41e467e5cf72570d997ac6c3a844e151258d4295%2Fview-executions.png?alt=media)

Each row shows the following information:

* **Pipeline Name**: The name of the pipeline and its execution ID. For a chained execution, this also shows the parent pipeline that triggered it.
* **Status**: The current status of the execution, such as `SUCCESS` or `FAILED`. For a failed execution, this also shows the stage where the failure occurred.
* **Trigger Summary**: How the execution was started, such as manually by a user or by another pipeline.
* **Update Summary**: Execution information for the Continuous Delivery (CD) and Database DevOps modules, such as the service and environment, or schema version and database instance, used in the execution.
* **Execution Start Time**: The user or trigger that started the execution, and how long ago it started.
* **Duration**: How long the execution took to run.
* **Pipeline Timeout**: The time at which the execution is set to expire, calculated from the execution start time and the pipeline's configured timeout duration. Harness calculates this value for every execution, regardless of its final status. This value reflects only the pipeline-level timeout, and does not account for stage-level or step-level timeouts. Hover over the value to view the exact expiry date and time. Select the column header, or use the sort dropdown, to sort executions by pipeline timeout. Executions with no pipeline timeout configured always appear at the end of the list, regardless of sort direction.

For account-level visibility into pipelines close to expiry across all projects and organizations, go to [Pipelines close to expiry](/harness-platform/use-harness-platform/pipelines/executions-and-logs/view-pipelines-close-to-expiry.md).

For detailed guidance on viewing executions in specific modules:

* [View builds](https://developer.harness.io/docs/continuous-integration/use-ci/viewing-builds): View build execution history and logs for build pipelines.
* [View test results](https://developer.harness.io/docs/continuous-integration/use-ci/run-tests/viewing-tests): View test execution results and reports for build pipelines with test steps.
* [Monitor deployments](https://developer.harness.io/docs/continuous-delivery/monitor-deployments/monitor-cd-deployments): Use dashboards to monitor deployment executions and track DORA metrics.
* [Executions management](/harness-platform/use-harness-platform/pipelines/executions-and-logs/executions-management.md): View and manage all queued and running pipeline executions across your account from a central location.
* [Download execution logs](/harness-platform/use-harness-platform/pipelines/executions-and-logs/download-logs.md): Download logs from any pipeline execution for offline analysis.

***

## View compiled YAML

A pipeline's compiled execution YAML is the YAML used for execution, including all resolved [runtime inputs](/harness-platform/use-harness-platform/variables-and-expressions/runtime-inputs.md), [expressions](/harness-platform/use-harness-platform/variables-and-expressions/runtime-inputs.md), and [variables](/harness-platform/use-harness-platform/variables-and-expressions/harness-variables.md).

Perform the following steps to view the compiled YAML for a pipeline execution:

1. Navigate to your pipeline and select **Execution History**.
2. Locate the execution that you want to inspect, select **More Options** (⋮), and then select **View Compiled YAML**.

Harness displays the compiled pipeline YAML for that execution, showing all resolved values.

***

## Compare executions

You can compare the compiled execution YAML for two executions to see what changed between them. This comparison helps you identify the changes that may have caused different execution results or failures.

Perform the following steps to compare two pipeline executions:

1. Navigate to your pipeline and select **Execution History**.
2. Locate an execution that you want to compare, select **More Options** (⋮), and then select **Compare YAML** or **Compare Pipeline Executions**.

   The execution where you selected **More Options** is automatically selected. If you do not want to compare this execution, deselect it and select a different execution.
3. Select another execution that you want to compare.
4. Select **Compare**.

Harness produces a diff of the pipeline YAML for the two executions. This diff helps you identify the changes between executions, and it can help with troubleshooting execution failures or unexpected behavior.

***

## Next steps

* [Download execution logs](/harness-platform/use-harness-platform/pipelines/executions-and-logs/download-logs.md): Download logs from pipeline executions for offline analysis and troubleshooting.
* [Retry failed executions](/harness-platform/use-harness-platform/pipelines/failure-handling/resume-pipeline-deployments.md): Resume pipeline executions from any successful or failed stage.
* [Troubleshoot pipeline executions](/harness-platform/use-harness-platform/pipelines/troubleshoot-pipeline-executions.md): Diagnose and resolve common pipeline execution issues.

{% @harness-feedback/feedback module="harness-ai" pagePath="harness-ai/use-harness-platform/pipelines/executions-and-logs/view-and-compare-pipeline-executions" %}