> For the complete documentation index, see [llms.txt](https://learn.capstorm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.capstorm.com/copystorm-restore/reference/tracker-database-tab/delete-records.md).

# Delete Records

The Delete Records tool deletes records from the Tracker Database. The most common use case is:

* The candidate scan found too many records. I want the application to forget about previously found records.

Using the Delete Records dialog requires making two decisions:

* Which records should be deleted.
* Which record statuses should be affected.

Default parameters delete all visible skipped and pending records.

![](/files/g4e5JCMPrHranTRDTmzQ)

* Records to Delete
  * “Visible”: Delete all records currently shown in the Tracker table, taking filters into account.
  * “Table”: Delete all records in the Tracker table, not taking filters into account.
  * “All”: Delete all records from all Tracker tables.
* Selected Record Status
  * Only delete records with the selected statuses.
* Limit Delete To
  * Records that have been deleted from the target Salesforce.
    * Only delete records that were previously restored and no longer present in the target Salesforce.
  * Records that are missing in the CopyStorm database.
    * Only delete records that were previously found in the CopyStorm database but no longer present.
* Other Tracker Data to Delete
  * Exceptions: Delete all Exception logging history from the tracker.
  * Skipped Record Reasons: Delete all record skip logging history from the tracker.
  * Restore History: Delete all Restore job logging history from the tracker.


---

# 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://learn.capstorm.com/copystorm-restore/reference/tracker-database-tab/delete-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.