> For the complete documentation index, see [llms.txt](https://www.tvrename.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.tvrename.com/menu/options-menu/ignore-list.md).

# Ignore List

When a ***Scan*** is run any “missing” episodes for shows in your media library are listed.

These may be genuine missing episodes or they may be “Specials”, that don’t fit the season/episode pattern but are still part of the show, for example: -

> My Favourite Show - S00E03 - Recap of Last Season

This may be something you want or it may just be adding to the “noise” in the ***Scan*** tab.

If it is “noise” you can highlight the row (or multiple rows if that fits better) and right click. A cut-down menu appears. If you select “Ignore Selected” the item is removed from the ***Scan*** results and appears in the “Ignore List”.

If, at a later date, you decide you wish to add the item, you can remove it from the Ignore list using the *Edit Ignore List* window, selecting the item in question and clicking `Remove`.


---

# 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://www.tvrename.com/menu/options-menu/ignore-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.
