> 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/main-dashboard/navigation/profile/playback.md).

# Playback

The Progress tab shows unfinished playback read live from connected players and playback providers.

Summary

The cards at the top show:

* **Unfinished** — unfinished playback found across your players.
* **Almost done** — items at 90 percent or more.
* **Stale** — items paused for more than 30 days.
* **Providers** — how many readable providers responded.

Unlike synchronized Profile tabs, Progress refreshes playback data directly from configured readable providers.

If one provider fails or times out, CrossWatch still shows available results. Provider issues appear separately.

#### Find and filter progress

You can filter by:

* **Search**
* **Media type**
* **Provider**
* **Progress** — Any progress, Under 25 percent, 25 to 50 percent, 50 to 75 percent, Over 75 percent, or Almost done.
* **Paused time** — Any time, Today, Last 7 days, Last 30 days, or Older than 30 days.

You can sort by:

* Recently paused
* Most watched
* Least watched
* Shortest remaining
* Highest rated
* Title, A to Z
* Provider
* Views

Progress supports:

* **Timeline** — grouped by paused date when sorting by **Recently paused**.
* **Grid**
* **List**

Choose 24, 48, or 96 items per page.

When matching playback exists on multiple providers, CrossWatch can show records together. Each record retains its provider information.

#### Playback actions

Available actions depend on the provider record's capabilities. They can include:

* **Edit progress**
* **Mark as watched**
* **Remove progress**

The maximum editable progress value is provider-specific. CrossWatch keeps normal edits below the provider completion boundary. Use **Mark as watched** to complete an item.

When an action targets multiple providers, CrossWatch reports completed, failed, and unsupported operations separately.

#### Bulk actions

With write permission, select multiple progress items and run supported playback actions in bulk.

You can select individual items, the visible page, or all matching results.

#### Refresh and provider settings

Select **Refresh** to query included playback providers again.

Administrators can open **Providers** to choose readable provider profiles for Progress. They can also set the slow provider timeout.

The default timeout is 20 seconds. The setting accepts values from 3 through 60 seconds.

Managed users can use playback actions only with assigned write access. Provider configuration remains an administrator function.

{% tabs %}
{% tab title="End users" %}
Use Progress for current unfinished playback across connected players.

This page shows live playback state. [History](/crosswatch/settings/configure-pairs/features/history.md) shows watched activity.
{% endtab %}

{% tab title="Power users" %}
Progress is available at `/profile#playback`.

Current endpoints include:

```
/api/playback_progress/items
/api/playback_progress/settings
/api/playback_progress/actions/update_progress
/api/playback_progress/actions/mark_watched
/api/playback_progress/actions/remove
/api/playback_progress/actions/bulk
```

Provider settings include only configured profiles that support readable playback progress.
{% endtab %}
{% endtabs %}

#### Related pages

* [Main dashboard](/crosswatch/main-dashboard.md)
* [History](/crosswatch/settings/configure-pairs/features/history.md)
* [Watchlist](/crosswatch/main-dashboard/navigation/profile/watchlist.md)


---

# 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/main-dashboard/navigation/profile/playback.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.