> 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/related-information/release-notes/version-0.10.md).

# Version 0.10

Release notes for CrossWatch v0.10.x, including Scrobbler, webhook, and reliability updates.

## Release 0.10.0

* Tag: `v0.10.0`

This release reworks the orchestrator and Plex adapter.

Sync planning, unresolved handling, and blackbox behavior are more reliable.

{% hint style="warning" %}
After upgrading, use [Maintenance](/crosswatch/settings/maintenance.md) to clean up state files.

This is recommended for every new minor release.
{% endhint %}

### Highlights

* **Orchestrator reworked**
  * Sync planning, apply handling, unresolved items, and blackbox promotion are more consistent.
* **Plex reworked**
  * Selected libraries, accepted writes, live confirmation, and episode matching are more reliable.
* **Events viewer**
  * Search SQLite-backed events for sync runs, item issues, and unresolved items.
  * Guide: [Events](/crosswatch/main-dashboard/tools/events.md)
* **Clearer issue visibility**
  * Sync output shows unresolved and blackboxed counts with item-level reasons.

### Fixes & improvements

* **Orchestrator**
  * Records clearer sync-run outcomes, including errors, unresolved items, and blackboxed items.
  * Promotes items to the blackbox using `promote_after` rules. The default is `3`.
  * Keeps unresolved, blackboxed, and failed-item handling separate.
  * Distinguishes accepted writes from confirmed provider state.
  * Refreshes snapshots after accepted writes when needed. This reduces stale comparisons.
* **Events and Analyzer**
  * Events groups sync runs with related item threads.
  * Run summaries include blackboxed item counts.
  * Analyzer readability and pagination now work better for large issue sets.
  * Unresolved-item details appear after a sync run when needed.
* **Plex**
  * History matching checks the selected library catalog.
  * Tracker-to-Plex writes resolve episodes more reliably.
  * History results retain show titles for episodes.
  * Cache handling respects server, user, and library changes.
  * Movie and episode duration handling is more accurate.
  * Playback Progress removals clear and verify before reporting success.
* **Watcher and dashboard**
  * Watcher enforces the library whitelist for every event.
  * The Playing Card shows episode time remaining when duration data exists.
  * Latest Ratings uses real rating timestamps when available.
* **Reliability and security**
  * Sync locking disables buttons and pair actions during a sync.
  * API errors no longer expose internal exception details.
  * Emby and Jellyfin history episodes match by show, season, and episode.
  * Client-side sync-log formatting is removed.

### Adapter versions

* Plex: `v2.0`
* SIMKL: `v1.3`
* Trakt: `v1.2`


---

# 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/related-information/release-notes/version-0.10.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.