> For the complete documentation index, see [llms.txt](https://docs.fullwhere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullwhere.com/documentation/documentation-en/reports/report-history.md).

# Report history

View generated reports, download their files, and access Fullwhere Brain analytics.

The report history centralizes the reports generated by your report configurations. Access it from **Reports** then **View history**.

## View generated reports

The table displays one report per line. It presents the following information:

| Column         | Description                                                         |
| -------------- | ------------------------------------------------------------------- |
| Name           | Name of the generated report with your potential variables replaced |
| Creation date  | Date and time the report was generated                              |
| Covered period | Period taken into account in the report                             |
| Scope          | Brand, group of locations, or location concerned                    |
| Status         | Report generation status                                            |
| Output         | Files and analysis available                                        |

Reports can be **in progress**, **available** or in **failed**. Files and analyses become accessible when the report is available.

## Filter history

Use the filters at the top of the table to quickly find a report. You can filter by:

* date ;
* configuration ;
* frequency ;
* target type ;
* scope.

You can combine several filters to refine the results.

## View a report's outputs

In the column **Output**, open or download the available items:

* the file **PDF** ;
* the file **Excel** ;
* the analysis **Fullwhere Brain**, when it has been enabled for the configuration.

The Fullwhere Brain analysis is available only for the reports concerned. It presents the insights generated from the data for the covered period.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fullwhere.com/documentation/documentation-en/reports/report-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.