> For the complete documentation index, see [llms.txt](https://docs.allganize.ai/allganize-alli-works-userguide-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allganize.ai/allganize-alli-works-userguide-en/usage-records-and-member-information/answer-style-app-usage-records.md).

# Answer-style app usage records

<figure><img src="/files/tNCKa3ABGGXnC2XEvkDm" alt=""><figcaption></figcaption></figure>

You can view the actual execution history and detailed records of 'response-type' apps in the usage history.

**Response-type**

* App name: The name of the app used is displayed.
* App input: The input content that the member actually entered is displayed.
* Document name: The name of the document the member used in that app is displayed.
* Final result: The final result generated by the app is displayed.
* Delete: You can delete the record.
* Status: You can check whether the app ended normally or not.
* Prompt: You can view the prompt history used in the app.
* Options: You can check which options were used to handle long inputs.

**Filter and Sort**

<figure><img src="/files/Kis1SgNFuguPudmaETjv" alt=""><figcaption></figcaption></figure>

Click the filter icon to open the filter/sort popup. When a filter is selected, it is displayed below the conversation list search box.

* Filter by conversation status. Because it is a response-type app, it is classified as completed, failed, or interrupted.
* Filter by member name. Multiple selections possible.
* Filter by app.
* Sort by time of last conversation.
* Filter by date/time. Based on conversation start time.


---

# 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.allganize.ai/allganize-alli-works-userguide-en/usage-records-and-member-information/answer-style-app-usage-records.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.