> 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/main/when-to-watch.md).

# Schedule

Once you have TV Rename up and running and behaving the way you want you’ll probably spend most of your time on this tab. If you wish you can make this tab open by default by changing the “Startup tab” setting in the [***Display***](https://www.tvrename.com/menu/preferences/display.md) tab of **Options>Preferences**.

<figure><img src="https://3508557057-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx0gPeIfHpbgTioNust1M%2Fuploads%2FtczZrcwvuHhdi9LxU7Te%2Fschedule-tab.png?alt=media" alt=""><figcaption></figcaption></figure>

Looking at the list in the main panel we see details of recent and future show episodes matching the TV shows found in the media library.

At the top of the panel episodes “Aired in the last 7 days” are shown (you can actually modify the number of days in the [***General***](https://www.tvrename.com/menu/preferences/general.md) tab of **Options>Preferences** if you wish).

In this example there are a number of episodes listed. A disk icon to the left of a show indicates that the episode was found in the media library and the magnifying glass to the left of a show indicates that the episode has aired, but cannot be found locally. Double clicking on a row thus indicated will do one of two things, set by “Double-click in Schedule does” in the [***Display***](https://www.tvrename.com/menu/preferences/display.md) tab of **Options>Preferences**:

* **Scan** (the default) scans that show and switches to the **Scan** tab.
* **Search** launches your default web browser (pointing to the search engine currently chosen on the toolbar, Google unless you have changed it) pre-loaded with search parameters to look for the missing file (configured in [**Options>TV Show Search Engines**](https://www.tvrename.com/menu/options-menu/search-engines.md)).

The next section indicates which shows already in the media library will be airing a new episode in the “Next 7 Days”.

“Returning Series” looks further ahead and lists the first new episode of each show found in the media library not already listed in “Next 7 Days”.

“Other Planned Episodes” shows the rest of the future episode information matching shows in the media library that the [data sources](https://www.tvrename.com/help-and-support/data-sources.md) know about.

The next two panels show (on the left) a summary for the episode highlighted in the main panel and (on the right) a calendar indicating the dates episodes were/will be broadcast (in bold type). The calendar interacts with the main and summary panels. Clicking on a bold date will highlight the show episode matching the date in the list above, and clicking on an episode in the main panel will cause the calendar to display that date. In either case the episode summary will be updated as well (if there is one).

**As mentioned elsewhere, the content presented by TV Rename is only as good as that found at the** [**data sources**](https://www.tvrename.com/help-and-support/data-sources.md) **(TMDB, TheTVDB and TVmaze) so please consider registering and helping to maintain their content - everybody benefits!**


---

# 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/main/when-to-watch.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.
