> 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/blueprint-architecture/sync/_mod_emby/progress.md).

# progress

Related:

* Pair setting: [Progress](/crosswatch/configure-pairs/features/progress.md)
* Technical blueprint: [Progress](broken://spaces/3rh5THg1PdhVsBt3GALo/pages/6mUNmCn3Ju6CJzYTrpZR)

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

### What syncs

This feature syncs **resume position** ("Continue Watching") for an Emby user.

### Supported media types

* Movies: ✅
* Episodes: ✅

### Reads vs writes

* Reads: Emby resumable items.
* Writes:
  * `add` upserts resume position.
  * `remove` clears resume position (sets it to `0`) when enabled.

### Key settings (per pair)

* `features.progress.enable`
* `features.progress.add`
* `features.progress.remove`
* `features.progress.min_seconds` (default `60`)
* `features.progress.delta_seconds` (default `30`)
* `features.progress.max_percent` (default `95`)

### Safety rules (important)

* Progress **never clears from absence**.
* Only an **explicit** `progress_ms = 0` can trigger a clear.
* Near-complete items (>= `max_percent`) are skipped.
  {% endtab %}

{% tab title="Power users" %}

### Index behavior

Emby indexes resumable items using the user Items endpoint.

* `PlaybackPositionTicks` → `progress_ms` (`ticks / 10,000`)
* `RunTimeTicks` → `duration_ms`
* `LastPlayedDate` → `progress_at`

### Write / clear behavior

Writes use the same UserData endpoint:

* Upsert: set `PlaybackPositionTicks` to the desired ticks.
* Clear: set `PlaybackPositionTicks` to `0`.

### Planner notes

Thresholds live in `diff_progress`:

* ignore progress < `min_seconds`
* only write when delta >= `delta_seconds`
* ignore progress >= `max_percent` of duration

### Code map

* `providers/sync/emby/_progress.py`
* `cw_platform/orchestrator/_planner.py::diff_progress`

### Matching notes

Progress depends on stable canonical keys.

Missing external IDs can cause resolution failures.
{% 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 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/blueprint-architecture/sync/_mod_emby/progress.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.