> 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/progress.md).

# Progress

Sync resume positions and optional Continue Watching removals.

Progress syncs **resume position**.

It keeps resume positions aligned across supported providers. To also copy titles removed from a media server's Continue Watching row, enable the optional removal sync below.

It does **not** mark items watched.

Use [History](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history.md) for watched state.

{% tabs %}
{% tab title="End users" %}

### What syncs

Progress syncs the position where playback stopped.

It does **not** treat a missing resume position as a clear request.

Watched history stays separate from progress sync.

### Pair controls

Per pair, you can control:

* **Enable**
* **Mode** — one-way or two-way
* **Add / Update**
* **Remove (clear)**

Clear support depends on the destination provider.

**Emby, Jellyfin, Silo and Tofa** support clears.

**Plex** does not support clears.

#### Anime episode mapping

This shows when SIMKL can receive progress in the pair.

It translates anime episode numbering before progress is written to SIMKL, using the local Anime ID database.

It needs global Anime ID Mapping to be enabled first.

It can heavily increase API calls when extra anime ID and episode lookups are needed.

### Sync Continue Watching removals

**Beta. Off by default.** When you remove a title from Continue Watching on one server, CrossWatch can hide the matching title on the other. This keeps the saved resume position and does not mark the title watched.

Both sides of the pair must be **Emby, Plex, Tofa or Silo**. Jellyfin and other providers are unsupported for this option, even if they support ordinary Progress sync.

1. Open the pair and select **Progress**. Turn on **Enable**.
2. Under **Progress | Options**, turn on **Sync Continue Watching removals**, then save.
3. Run a normal sync with **Dry run** off to record the current rows. This first run does not copy earlier removals.
4. Remove a title from Continue Watching on the source server. A later sync can hide it on the destination. Use a normal sync to apply eligible hides automatically, or Interactive Sync to review them first. In a two-way pair, removals can travel in either direction.

This option works separately from **Remove**, which controls clearing resume positions. You do not need to enable Remove or change the one-way deletion mode to copy these hides.

#### What gets hidden

| Destination | Effect                                                      |
| ----------- | ----------------------------------------------------------- |
| Emby        | Hides the movie or show's Continue Watching card.           |
| Plex        | Hides the movie or matching episode.                        |
| Tofa        | Hides the movie or whole show.                              |
| Silo        | Hides the movie or show's card, including its next-up card. |

#### Review before hiding

1. On the pair, select **Run** to open [Interactive Sync](https://wiki.crosswatch.app/crosswatch/main-dashboard/interactive-sync.md).
2. Look for **Hide from Continue Watching** under **Progress**. Check the title and destination; a two-way pair can propose hides on either server.
3. Keep the hides you want selected and choose **Apply selected**. Previewing the plan does not hide anything. Applied hides keep the saved resume positions.

The review uses the Continue Watching data it captured. If someone has played or changed a title since you opened the review, use **Refresh plan** and check the proposals again before applying.

**Deselecting postpones a hide for this apply only.** It can return in the next review or be applied by a later normal or scheduled sync. Failed hides are also retried when still eligible. To stop future removal syncing for the pair, turn off **Sync Continue Watching removals**.

Already pending hides can survive changes to the row, including the row becoming empty or the title getting older than the remaining cards. Later runs still check that source progress is unchanged and the destination has no newer progress.

#### Limits and checks

* Detection needs saved progress that stays unchanged after the title leaves the row. Titles without saved progress are not covered. Matching episodes need the same episode on both servers.
* CrossWatch does not detect new removals from an empty source row, missing playback timestamps or titles older than the remaining row. Already pending hides follow the retry rules above.
* Newer destination progress protects the title; for a show, newer progress on another episode also protects it.
* **Specials (Season 0)** and manual blocks are respected.
* Undoing a removal is not synced. Restore the title separately on each server if needed.
* **Dry run** does not hide titles or record a new row snapshot. In Interactive Sync, **Apply selected** can ask you to confirm a one-time write while leaving global Dry run enabled.

Open [Events](https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/events.md) and look for **Hide from Continue Watching** to review attempts and failures. Resume-position sync still follows the other Progress settings.

### Advanced playback progress

These settings live on the pair.

Different pairs can use different progress rules.

#### Minimum seconds

Default: `60`

Resume positions below this value are ignored.

A stop in the first minute does not sync with the default.

Use `0` to disable this filter.

#### Change threshold

Default: `30`

CrossWatch writes progress only when the source and destination differ by at least this value.

This reduces noisy writes from small player timing differences.

Use `0` to consider every difference.

#### Ignore near complete

Default: `95` percent

Positions at or above this value do not sync as unfinished progress.

This lets [History](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history.md) own the watched state.

Enable History if you rely on this setting.

#### Replay watched items

Default: disabled

By default, CrossWatch does not write unfinished progress over a watched destination item.

With this enabled, CrossWatch can mark the destination unwatched and restore the source resume point.

Use it only for deliberate rewatches.

#### Timestamp tolerance

Default: `30` seconds

Accepted range: `0` to `300` seconds

If the destination timestamp is newer than the source by more than this value, CrossWatch skips the write.

Increase it when minor clock drift blocks valid writes.

#### Specials (Season 0)

Default: enabled

Includes Season 0 episodes.

Turn it off to skip them on both sides of the pair.

#### Only items in destination library

Default: enabled for new pairs with a supported destination. Existing pairs keep their saved choice.

Skips resume positions for movies and episodes that are not in your media server library.

It is explained in full further down this page.

<details>

<summary>Change threshold examples</summary>

With a threshold of `30` seconds:

* Source `20:00`, destination `19:45` → no write
* Source `20:00`, destination `19:20` → write allowed

</details>

{% hint style="info" %}
Recommended defaults:

* Minimum seconds: `60`
* Change threshold: `30`
* Ignore near complete: `95`
* Replay watched items: disabled
* Timestamp tolerance: `30`
* Specials (Season 0): enabled
* Only items in destination library: enabled for supported destinations
  {% endhint %}

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FlHH1dJ1ekCQJbVQHNBO5%2Fimage.png?alt=media&amp;token=c4f1c40b-3b66-4912-8b3c-d1dd659c381d" alt=""><figcaption></figcaption></figure>

### Skipping titles that are not in your library

This is what **Only items in destination library** does.

Trackers and other servers hold resume positions for titles you may not have.

Without this option, CrossWatch tries to write all of them and most of them fail.

With this option, CrossWatch checks your library first and leaves out what is not there.

#### Compatibility

This option applies only when the listed provider is the **destination**.

| Feature   | Plex | Emby | Jellyfin | Kodi | Silo | Tofa |
| --------- | ---- | ---- | -------- | ---- | ---- | ---- |
| History   | Yes  | Yes  | Yes      | Yes  | Yes  | Yes  |
| Ratings   | Yes  | No   | No       | Yes  | Yes  | No   |
| Progress  | Yes  | Yes  | Yes      | Yes  | Yes  | Yes  |
| Watchlist | No   | Yes  | Yes      | No   | No   | No   |

In a two-way pair, it filters only the direction that writes to a supported destination.

**You see it when**

* The destination is Plex, Emby, Jellyfin, Kodi, Silo or Tofa.
* Or the pair is two-way and one side is one of those.

**Enabled (default for new pairs)**

* Interactive Sync only shows positions that can actually be written.
* No write attempts for titles your server does not have.
* Missing titles no longer fill up unresolved and blackbox.
* A title you add to your library later gets its position on the next sync.
* Adds a library check to every run, usually a few seconds.

**Disabled**

* Sync works as it always has.
* Every position is attempted, including title matching when Strict ID matching is off.
* Missing titles show as unresolved and get blackboxed after three failed runs.

{% hint style="info" %}
Position changes are always synced. A title your server already has a resume position for is never skipped.

Only titles without a position on the destination are checked against your library.
{% endhint %}

{% hint style="warning" %}
The check matches on IDs only. A title that is in your library under a different ID is skipped too.

Leave it off if your library has missing or wrong IDs.
{% endhint %}

**Good to know**

* Skipped items show in Interactive Sync as **Not in library**. They are hidden by default, with a count you can click.
* Only movies and episodes are checked.
* Your Progress library whitelist still applies. A title in a library that is not whitelisted counts as not in the library.
* Items without any usable ID are not checked. They sync the same way as before.

### Progress vs Playback

**Progress** updates when the pair runs.

**Playback** reads the provider live.

The numbers can differ between those views.

That is normal.
{% endtab %}

{% tab title="Power users" %}

### Planning vs write scope

These settings affect planning for all supported progress pairs:

* **Minimum seconds**
* **Change threshold**
* **Ignore near complete**

These settings mainly affect writes to **Plex**, **Emby**, and **Jellyfin** destinations:

* **Replay watched items**
* **Timestamp tolerance**

**Only items in destination library** affects planning for **Plex**, **Emby**, **Jellyfin**, **Kodi**, **Silo**, and **Tofa** destinations.

It runs after every other progress filter, so it only sees positions that already passed them.

**Nuvio**, **PublicMetaDB**, and **CrossWatch local** use their own write rules.

### Regression handling

When the source position is behind the destination, CrossWatch checks timestamps first.

Without usable timestamps, it does not move progress backward.

In two-way mode, the newest usable progress usually wins.

If timestamps are missing, the higher position wins.

### Clear behavior

These rules apply to clearing resume positions. [Continue Watching removals](#sync-continue-watching-removals) use their own opt-in setting and preserve positions.

Progress does **not** clear just because the source has no resume position.

Clear behavior still depends on pair remove settings and provider support.

{% hint style="warning" %}
One-way remove behavior uses **One-Way Remove mode (Deletions based on Source)** in [Global settings](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/global-settings.md).

If you want source-side clears to mirror to the destination, you usually want **Mirror** mode.
{% endhint %}

Progress clears are tombstone-driven.

That means a clear can take two runs:

1. CrossWatch records that the source item disappeared.
2. The next run treats that disappearance as real and applies the clear.

See [Global settings](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/global-settings.md).

### Additional write protection

Before writing to **Plex**, **Emby**, or **Jellyfin**, CrossWatch also skips when:

* the item is actively playing on the destination
* source and destination are the same provider instance
* the source has no usable progress timestamp
* the destination is newer than the allowed tolerance
* the destination is watched and replay mode is off
* the positions are already materially equal

These checks prevent scheduled syncs from overwriting newer destination activity.

### Provider notes

* **Plex** does not support clear
* **Plex** timestamps can be delayed or missing
* **Emby** clears by setting progress to `0`
* **Jellyfin** clears by setting progress to `0`
* **Tofa** requires resume positions of at least one minute and skips watched items. See [Tofa](https://wiki.crosswatch.app/crosswatch/settings/synchronization/media-servers/tofa.md).
* **Nuvio** supports progress removal when pair removal is enabled
* **Replay watched items** is implemented for Plex, Emby, and Jellyfin destinations

### Related

* [Features](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features.md)
* [Configure Pairs](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs.md)
* [Playback](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/profile/playback.md)
* [History](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history.md)
  {% endtab %}
  {% endtabs %}


---

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