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

# Results and failures

> A result records what happened during execution. The runner identifies the test’s status; the detailed conversation shows the outcomes of its checks and simulation…

## Overview

<a id="how-it-works" />

<a id="when-to-use-it" />

A result records what happened during execution. The runner identifies the test’s status; the detailed conversation shows the outcomes of its checks and simulation segments.

<a id="use"></a>

## When to use it

Investigate results that differ from the expected behavior.

Use the detailed result when a response, route, tool call, or simulated outcome differs from what you expected. A canceled run should not be treated as evidence that the expected behavior passed.

<a id="model"></a>

## How it works

Inspect the status, checks, simulation results and execution evidence.

| Result layer | What to inspect |
| --- | --- |
| Overall test status | Passed, Failed, or Canceled once finished; pending activity remains in progress. |
| Agent-turn check | The response, routing, or tool check’s Pass/Fail result and reason. |
| Simulation segment | Generated messages, the evaluated outcome, and its reason. |
| Conversation logs | The execution evidence behind the visible exchange. |

Compare the saved expectation with the actual evidence. A response can sound appropriate while a routing or tool check still fails. Credits-limit notifications can also appear during execution; consult [credits and costs](/docs/platform/rehearsal/reference/costs) when a run cannot proceed.

<a id="example"></a>

## Example

Trace a missing tool call before changing the expectation.

If an order lookup tool was expected but never called, inspect the conversation and logs before changing the assertion. The agent may have needed more user information, or the starting variables may differ from the intended scenario. A retry should confirm the original expectation after a deliberate correction.

### Next steps

- [Response expectations](/docs/platform/rehearsal/tests/response-checks)
- [Routing expectations](/docs/platform/rehearsal/tests/routing-checks)
- [Tool expectations](/docs/platform/rehearsal/tests/tool-call-checks)
- [Simulation outcomes](/docs/platform/rehearsal/simulations/results)
- [Retry a run](/docs/platform/rehearsal/runs/history)
