> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/extracting-data-into-pdi/work-with-the-streamlined-data-refinery/install-and-configure-the-streamlined-data-refinery/clean-up-the-all-requests-processed-list.md).

# Clean up the All Requests Processed list

You can delete items from the **All Requests Processed** list in order to clean your **Latest Requests** list.

**CAUTION:**

Deleting entries from the **Latest Requests** list also deletes the tables that contain your data and removes the metadata or Analyzer data source from the list of data sources that appear in PUC.

Follow these quick steps to remove items from the **Latest Requests** list.

1. Click on **All Requests Processed** to open the **Latest Requests** list.
2. Click on **Edit**.
3. Select the check box next to the data sources that you want to delete.

   ![Select data sources to delete](https://773338310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYwnJ6Fexn4LZwKRHghPK%2Fuploads%2Fgit-blob-502b0f8de8dbe9990e5de1d5e79d941ba009b6b5%2FSDR_CleanList.png?alt=media)
4. Click on **Delete** to remove the selected data sources from the list.

   ![Cleaned-up list](https://773338310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYwnJ6Fexn4LZwKRHghPK%2Fuploads%2Fgit-blob-56e9adfb86631e3b30247035c7106cde458d7e47%2FSDR_ListCleaned.png?alt=media)

Your **All Requests Processed** list is now cleaned and the corresponding tables are deleted.


---

# 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.pentaho.com/pdia-data-integration/extracting-data-into-pdi/work-with-the-streamlined-data-refinery/install-and-configure-the-streamlined-data-refinery/clean-up-the-all-requests-processed-list.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.