> For the complete documentation index, see [llms.txt](https://docs.iotify.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotify.io/getting-started/analyze-the-results.md).

# Analyze the results

After your simulations have completed running, you will want to see how many requests went through, how many failed and other data related to the simulation.&#x20;

You can find all of the data related to the simulation run in a well-organized manner on the Results page. Here, you will see a list of all the different simulation jobs with an overview of their results. The status of currently running tests are updated in real-time.&#x20;

![](/files/McnKklds1r4mqJLZy21O)

On this page, you can also stop an ongoing simulation job, delete an old job or restart a completed job. All of these can be done by clicking on the respective icons under the Operations column.

If you want to know about more detailed results for a specific job, you can do so by clicking on the folder icon under the Operations column. Once you click that, the detailed results for the specific job will be opened. &#x20;

The results are divided into several tabs: Summary, Logs, State and Payload. Let's go through them one by one.

{% hint style="info" %}
If you are sending more messages or connecting more clients than what your server could handle, every client is eventually going to wait for its turn to connect and send, thereby stretching the overall test duration. It is important to carefully tune timeout values in your template to handle this worst case, otherwise, the iteration will be marked as failed.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.iotify.io/getting-started/analyze-the-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
