> 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/show-skipped-reasons.md).

# Show Skipped Reasons

The Show Skipped Reasons tool displays the reason(s) why CopyStorm/Restore failed to restore records.

Skipped records are organized using two parameters:

* Category — the general type of reason a record was skipped.
  * Most reasons use the category “Default” but some, like Lead, may use the category “Unsupported”.
  * “Unsupported” reasons are due to the Salesforce API not supporting the operation.
* Table — the name of a table with skipped records.

These parameters may be set at the top of the Show Skipped Reasons dialog. If not set, all values are displayed. In addition a search string may be specified, limiting displayed records to those whose reason contains the search string.

The following additional operations are supported:

* The “Delete” button deletes skipped reasons from the tracker database.
* The “Export” button saves skipped reasons to a CSV file.

![](/files/jrNNVhEIBwVcdZAfwzDt)


---

# 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/show-skipped-reasons.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.