> For the complete documentation index, see [llms.txt](https://docs.loadmill.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loadmill.com/general/account-settings/analytics/flow-run-history.md).

# Flow Run History

We understand how crucial is to review API automated test runs, see the test flow timeline and easily detect how often and when the test flow fails.

All the above can be done by using the Flow Run History feature.

Navigate to the Test Suite Run => Enter a relevant Test Flow => Click on the "FLOW HISTORY" button.

![](/files/9xLmxYOsNPMLSou3TeKR)

You are redirected to the Flow Run History page where you can see all runs of the test flow, apply various filters and download the table as CSV for sharing with other colleagues:

![](/files/Q7ir6qq7YtxoxwP9Hofs)

Stay tuned, more helpful features and integrations with reporting platforms are coming soon! 🙃


---

# 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.loadmill.com/general/account-settings/analytics/flow-run-history.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.