Execution logs

Understand the execution detail view, how to read stage and step logs, and how to re-run a pipeline.

When you select an execution from the pipeline-level Executions tab or the project-level Executions tab, Harness opens the execution detail view for that run.

What you will learn

• How to read the execution header metadata: status, trigger, duration, and who ran the pipeline

• How to navigate the stage and step tree in the Console view to find a specific step's logs

• How to view logs, inputs, outputs, and delegate information for any step

• What information is available on the Pipeline, Inputs, Artifacts, and other execution tabs

Execution header

The header shows the pipeline name and execution number (for example, Hello World Pipeline #1) along with key metadata:

Field	Description
Status	Final state of the run: Success, Failed, Aborted, etc.
Started	When the execution started.
Finished	When the execution completed.
Duration	Total time the execution took.
Trigger	What started the run: Manual, Webhook, Schedule, or Artifact.
Triggered by	The user or system identity that triggered the run.

The header also has two action buttons:

• Re-run: starts a new execution of the same pipeline using the same inputs.

• View Pipeline: opens the pipeline in Pipeline Studio.

Console view

The Console tab is the default view. It shows a stage and step tree on the left and the log output on the right.

Stage and step tree: lists every stage and step in the execution with its status and duration. Select a step to load its logs on the right.

Log panel: displays the raw output from the selected step. Use the search bar to find specific lines. The log panel has its own tabs:

Tab	Description
Logs	Raw console output from the step.
Input	The inputs passed into the step at runtime.
Output	Output variables exported by the step.
Delegate	The delegate that ran the step, including its identifier.
Task logs	Lower-level task logs from the Harness runner.

Other execution tabs

Tab	Description
Pipeline	The pipeline YAML as it was at the time of the run, frozen at that execution.
Inputs	The runtime input values used for this execution.
Policies	Policy evaluation results for the run.
Artifacts	Artifacts produced by the run.
Supply Chain	Software supply chain metadata (SBOM, attestations).
Tests	Test results reported by test steps.
Annotations	Custom annotations added to the execution.
Vulnerabilities	Security scan results linked to this run.
Coverage	Code coverage results reported by test steps.

Next steps

• Go to Pipelines to understand the pipeline model and how to create a pipeline.

• Go to Pipeline Studio to open a pipeline and trigger a new run.

• Go to Input sets and overlays to save and reuse runtime input values across runs.