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

# Experiment results

> Review experiment outputs, failures, usage, and request details

Use run results to compare candidate behavior across dataset rows.

The default view is a result-cell table. Each row represents one dataset row run against one candidate.

## Result columns <a href="#result-columns" id="result-columns" />

Result tables can include:

| Column         | Meaning                                                              |
| -------------- | -------------------------------------------------------------------- |
| Dataset row    | The row position from the dataset version                            |
| Candidate      | The prompt candidate                                                 |
| Status         | Pending, running, completed, failed, cancelled, or another run state |
| Output preview | Short preview of the generated output                                |
| Duration       | Time spent on the result cell                                        |
| Tokens         | Token usage when available                                           |
| Cost           | Cost recorded for the result cell                                    |
| Metadata       | Dataset row metadata, shown as a compact count with a hover detail   |
| Request ID     | The linked request created by the normal prompt execution flow       |

## How do I filter results? <a href="#filter-results" id="filter-results" />

Use the filters at the top of the result view.

You can filter by candidate, status, dataset row, or text search.

Use filters when you want to focus on failures, compare one candidate at a time, or inspect a specific case.

## How do I export results? <a href="#export-results" id="export-results" />

Click **Export CSV** from the run results table.

The export includes every result that matches the current filters, not only the visible page.

CSV exports include dataset inputs, expected output, metadata, candidate details, output or error text, request IDs, timing, token usage, cost, and timestamps.

## How do I inspect a result? <a href="#inspect-result" id="inspect-result" />

Click a result row.

Fetch Hive opens the same request detail sheet used by the normal logs area. This keeps experiment review aligned with live prompt request inspection instead of using a separate experiment-only detail surface.

Use request details when you need provider settings, inputs, metadata, trace availability, cost, timing information, or completions.

If a result failed before a request was created, the row remains visible with the failure status and any stored output or error summary.

## How expected output appears <a href="#expected-output" id="expected-output" />

If the dataset row includes `expected_output`, use it as the reference answer while reviewing results.

Evaluator execution is not enabled yet. This means Fetch Hive does not currently mark a result correct or incorrect automatically.

See also: [Datasets](./datasets), [Run an experiment](./running-experiments), and [Log history](../monitoring/log-history)