Workflow Execution Details

Overview

The Workflow Execution Details view is the evidence view for a single executed workflow. Use it to pinpoint root cause by inspecting exactly which steps ran, what was sent and received at each node, which validations failed, and how variables flowed through the run.

Opening a report (View Report button)

From Reporting > Execution summary, select a run and click View Report. For workflow (integration) runs, this opens the pack-level report. In the Workflow Execution Details table, click View Report (eye icon) on the row for the workflow you want to inspect. That opens the high-level workflow execution view (summary, node status, and success rate). From there, click View Report (or View Details) to open the detailed workflow report with full request/response and assertion outcomes per node.

What you'll typically see

• Run metadata: workflow name, project, environment, execution date/time, duration, executed by, execution type (Manual/Automated), success rate.
• Node summary: counts for passed, failed, error, and skipped nodes; node distribution (e.g. pie chart) and total nodes.
• Node executions (sequential): for each step, node name, status, duration, and (in the detailed report) request details (URL, headers, params, body), response details (status code, headers, payload), validation results (expected vs actual), and extracted variables.
• Execution logs: unified execution log with workflow- and node-level trace lines, timing, and any errors or skip reasons.
• Final variables: workflow-level variables available at the end of the run (when present).
• Errors: any workflow- or node-level errors and failure messages.

How to debug efficiently

1. Start with the first failed or error node — it often explains why later steps were skipped or failed.
2. If a step's status code is wrong, check auth (tokens, credentials) and environment configuration first.
3. If a schema or contract validation fails, compare the response payload in that node to the expected contract or schema.
4. Re-run the workflow (or a smaller scope) to reproduce the issue consistently and confirm fixes.

Related articles

• High level test report
• Detailed test report
• Debug logging