> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quixa.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Execution Results & Subflow Inspection

> Inspect chronological execution timelines, request/response payloads, latency metrics, and nested subflow hierarchies.

When executing workflows on the canvas or through regression suites, Quixa provides deep diagnostic visibility through the **Execution Results Panel** and the **Subflow Results Viewer**.

```
┌────────────────────────────────────────────────────────────────────────────────────────┐
│  ▶️ Execution Run #1042 — Passed (All 4 steps successful)                     ⏱️ 780ms   │
├────────────────────────────────────────────────────────────────────────────────────────┤
│  1. [POST] /auth/login         [200 OK]      120ms   [1/1 Attempts]   Assertions: 2/2  │
│  2. [POST] /customers          [201 Created] 210ms   [1/1 Attempts]   Assertions: 3/3  │
│  3. 📦 Subflow: ProvisionCard  [200 OK]      340ms   [qComponent]     Assertions: 5/5  │
│     ├── 3.1. [POST] /cards/issue             140ms                                     │
│     ├── 3.2. [POST] /cards/pin/set           110ms                                     │
│     └── 3.3. [GET]  /cards/status            90ms                                      │
│  4. [POST] /notifications/sms  [200 OK]      110ms   [1/1 Attempts]   Assertions: 1/1  │
└────────────────────────────────────────────────────────────────────────────────────────┘
```

***

## 1. Execution Results Panel (`ExecutionResultsContent`)

The Execution Results Panel opens along the bottom of the canvas immediately upon launching a flow or step:

### Status Badges & Metrics

* **HTTP Status Code**: Color-coded pill (`200 OK`, `201 Created`, `400 Bad Request`, `500 Error`).
* **Latency Benchmarks**: Precise millisecond duration (e.g., `334ms`).
* **Attempt Counters**: Shows network or assertion retry attempts (e.g., `1/1` or `2/3`).
* **Component Badges**: Identifies control flow, script, and synchronization nodes with `qComponent` chips.

### Interactive Request & Response Inspector

Selecting any step in the timeline opens a three-pane inspector:

1. **Request Details**: Dispatched URL, query parameters, resolved headers, and request body.
2. **Response Viewer**: Formatted, syntax-highlighted JSON response viewer with one-click copy and search.
3. **Assertions Breakdown**: Displays every evaluated rule with pass/fail badges, expected values, and actual outputs.

***

## 2. Hierarchical Subflow Inspection (`SubflowResultsViewer`)

When workflows incorporate modular **Subflows**, execution details are not flattened or obscured. The **Subflow Results Viewer** maintains complete hierarchical visibility:

### Step Drill-Down

Clicking on any subflow node in the execution timeline expands a nested execution tree:

* View every internal node executed within the subflow in exact chronological order.
* Inspect individual sub-node request payloads, response envelopes, and latency contributions.
* Review assertions evaluated inside the subflow independently from parent flow assertions.

### Root-Cause Isolation

If a subflow step fails:

* The parent subflow node flags the failure with a red indicator.
* Expanding the subflow immediately pinpoints the exact internal node and assertion that failed, eliminating manual log scraping.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.