> For the complete documentation index, see [llms.txt](https://karini-ai.gitbook.io/karini-ai-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://karini-ai.gitbook.io/karini-ai-documentation/recipes/recipe-run-report.md).

# Recipe run report

The **Recipe Run Report** enables users to access detailed insights and execution results for each individual recipe run. This comprehensive report provides key metrics related to the success and failures of the recipe run, allowing users to review and analyze the processing outcome.

#### Accessing the Recipe Run Report

To view the report for a specific recipe run, follow these steps:

1. **Navigate to the Recipe Page**: Go to the relevant recipe.
2. In the recipe page interface, locate and click the **Action** button to display available options.  &#x20;

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

3. From the action options, select **View runs** to access a list of all recipe executions.

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

4. For each recipe run listed, the **View Report** button will be available next to its corresponding entry.
5. Select the **View Report** button next to the relevant recipe run to open the detailed report for that specific execution.

<figure><img src="/files/36opDmjsjTI9cKvWFrTu" alt=""><figcaption></figcaption></figure>

6. Once a recipe has been executed at least once, the **View Report** button and the corresponding recipe run details will become available.

#### Report Details

Upon clicking **View Report,** the system generates a detailed **Knowledge Base Ingestion Report** for the selected run, which provides the following information:

**1. Summary Statistics**

* **Total Files**: The total number of files processed during the recipe run.
* **Successful**: The count of files that were successfully ingested.
* **Failed**: The number of files that encountered errors during ingestion.
* **Deleted**: The number of files that were removed from the dataset (if applicable).
* **Success Rate**: The percentage of files that were successfully processed compared to the total files ingested.

**2. Run Metadata**

* **Date**: The timestamp of when the report was generated.
* **Run ID**: The identifier associated with the current recipe run.
* **Recipe ID**: The unique identifier for the recipe associated with the run.

**3. Error Details (Failed Items)**

The **Failed Items** section lists all files that failed to process during the run. For each failed item, the following details are provided:

* **Item ID**: A unique identifier for the failed file.
* **Source Reference**: The location or path of the source file.
* **Error Message**: A description of the error that occurred .

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


---

# 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://karini-ai.gitbook.io/karini-ai-documentation/recipes/recipe-run-report.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.
