# Review Results

Once an exploration completes, open the run detail view to inspect what Duku found.

### What to review

#### State graph

The graph shows every discovered page and how states connect. Nodes are states. Edges are actions like clicks, form submissions, and navigations.

#### Run replay

Each run includes a live recording of the full browser session.

Use it to watch every step Duku took, see where a flow changed, and confirm what happened before an error appeared.

#### Errors

Review:

* Runtime errors
* Network request failures
* Broken interactive elements
* Console errors and warnings

Each error includes the page where it occurred and a screenshot from that state.

#### Screenshots

Every state transition includes a full-page screenshot. Use them to verify what Duku actually saw.

{% hint style="info" %}
One exploration gives you a useful snapshot. Multiple explorations improve graph coverage over time.
{% endhint %}

### Continue with

* [Goals & Intent Tests](/core-concepts/goals-and-intent-tests.md)
* [GitHub Action](/integrations/github-action.md)
* [API Keys](/integrations/api-keys.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.duku.ai/getting-started/review-results.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.