> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history/rewatches.md).

# Rewatches

Rewatches keep repeated plays as separate history events.

Normal history stores watched state and the latest watched time. Rewatches preserve every individual play.

For example, three plays of one movie remain three history events.

### Supported providers

Rewatches currently work with:

1. Trakt
2. SIMKL
3. PublicMetaDB
4. Floppy
5. MDBList
6. Scrob
7. CW Tracker

Each side of the connection must support the required capability.

For a one-way connection, the source must read rewatch events. The target must read and write them.

For a two-way connection, both providers must read and write rewatch events.

Normal history synchronization remains available without this support.

### Enable Rewatches

Configure Rewatches for each connection.

1. Open the connection.
2. Select **History**.
3. Enable **History**.
4. Enable **Rewatches**.
5. Save the connection.

CrossWatch then compares individual watch events. It no longer treats all plays as one history entry.

Each play keeps its own watched timestamp. Supported providers preserve repeated watches during synchronization.

### SIMKL requirements

SIMKL supports Rewatches with **Pro** and **VIP** accounts.

Without either account level, SIMKL cannot synchronize Rewatches.

### When to enable it

Enable Rewatches when repeated watches should remain in your tracker history.

Use normal History when watched state alone is enough.

Rewatches affect **History** only. They do not affect Watchlist, Ratings, or Playback Progress.


---

# 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://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history/rewatches.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.