# Workflow Execution Details

> Second reporting step for Workflow runs only: per-workflow node summary, node table, and View Report to open the detailed report for a node.

Source: https://totalshiftleft.ai/help-center/product-documentation/workflow-execution-details

## Overview

**Workflow Execution Details** is the **middle** reporting step for **Workflows** run type only. It sits between the [High-level test report](/help-center/product-documentation/high-level-test-report) (workflow pack summary) and [Detailed Test Report (Workflow)](/help-center/product-documentation/detailed-test-report-workflow) (full workflow-node evidence).

**Functional** runs skip this page: they go from high-level test list directly to the detailed test report.

## How you get here

1. Open [Test reporting](/help-center/product-documentation/test-reporting).  
2. Choose a row with **Run type** **Workflows** and select **View report**.  
3. On the **High-Level Test Report**, in **Workflow execution details**, select **View report** (eye icon) on the workflow row you need.  

## What you’ll see

- **Execution summary** — cards for execution date/time, duration, executed by, integration or workflow name, project, environment, execution type, success rate (or similar).  
- **Node execution summary** — counts for passed, failed, error, skipped, and total nodes; often shown as summary cards and a **node distribution** chart.  
- **Node executions** table — each workflow **node** (step): node name, status, duration, error message when present, and **View report** to drill into that node.  

Use this view to see **which node failed** and how many steps succeeded before a failure.

## Next step: detailed report

Select **View report** on a node row to open [Detailed Test Report (Workflow)](/help-center/product-documentation/detailed-test-report-workflow) for that node.

## How to debug efficiently

1. Start with the **first failed or error node** — later steps may be skipped or misleading.  
2. If a node shows an unexpected status code, check authentication and environment configuration.  
3. Open the detailed report for that node to compare request, response, and validation results.  
4. Re-run the workflow or a smaller scope after fixes.  

## Related articles

- [Test reporting](/help-center/product-documentation/test-reporting)
- [High-level test report](/help-center/product-documentation/high-level-test-report)
- [Detailed Test Report (Workflow)](/help-center/product-documentation/detailed-test-report-workflow)
- [Debug Logging](/help-center/product-documentation/debug-logging)