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

# Events

Review titles, sync runs, watching, ratings, captures and backups, with results per destination.

Open **Tools → Events**, or select **Events** on the Main dashboard. The **Activity** page shows what CrossWatch attempted, where it succeeded and what needs attention.

{% hint style="info" %}
Events records activity. It does not change provider data, repair items or retry operations. Use [Analyzer](https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/analyzer.md) to compare current provider data.
{% endhint %}

### Choose a view

Choose **Sync**, **Watching & ratings**, **Captures**, **Backups**, **Audits** or **Statistics**, depending on your access. Backups is administrator-only; Audits is available to administrators outside a profile-scoped view.

**Titles** is the default for Sync and Watching & ratings. Sync also offers **Runs**. Use **Raw events** for individual recorded events. Captures, Backups and Audits use **Grouped** or Raw events. Your selected view is remembered in this browser.

On mobile, use **View** to choose the activity category. Open a row for details, then select **Back to events** to return. The **Filters** button in the search bar opens the filter sheet.

### Titles

In **Sync → Titles**, each title appears once per run, with its source, actions and results for each destination. Episode rows include the season and episode number. A title sent to several destinations can succeed at one and fail at another.

Use the shortcuts above the list: **Everything**, **Needs attention**, **Watched**, **Ratings**, **Watchlist**, **Collections** or **Removals**.

Open a title to inspect:

* **Path** — the source, destination results and recorded reasons. Later activity can help you see whether another attempt succeeded.
* **Where it comes from** — the likely origin of the item on each destination, based on current data. This can differ from the historical activity.
* **Earlier** — related activity for the same title.
* **Sessions** — playback sessions, when available in Watching & ratings.

For a sync title, **Show this run** opens its run summary and **View logs** opens the relevant [log](https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/logs.md).

| Destination result | Meaning                                                                            |
| ------------------ | ---------------------------------------------------------------------------------- |
| **Done**           | The operation succeeded.                                                           |
| **Failed**         | The operation failed or could not be resolved; read the reason.                    |
| **Skipped**        | CrossWatch did not send or complete the operation; read the restriction or reason. |
| **Already there**  | The destination already had the recorded state.                                    |
| **In progress**    | No final result has been recorded yet.                                             |

Title details are not a complete inventory of a large sync. Successful item details are limited, so run totals can exceed the titles shown. Check **Runs** for the overall result.

### Sync activity and runs

The **Sync activity** calendar is inside Events on the **Sync** tab.

* Color it by **Changes**, **Runs** or **Failures**.
* Choose **3 months**, **6 months** or **1 year**. The initial period is three months on phones and one year on larger screens; Changes is selected initially.
* Select a day to filter the list. Remove its filter chip to clear the date selection.
* On phones, expand **Sync activity** if it is collapsed, then scroll the calendar horizontally to see more weeks.

Choose **Runs** to browse runs for the selected day. Without a day selected, it opens the latest active day in the calendar. Runs are grouped by pair; **Show** expands runs without changes. Use **Filter runs…** to find a connection, feature or result.

Open a run to see its changes, failures, duration and recorded titles. For a run with several pairs, choose a pair or **All pairs**. Select a title for its destination results, or **View logs** for the execution details. **Show all** opens the longer title list when more titles are available.

### Watching and ratings

Select **Watching & ratings → Titles** for playback and rating activity with results across destinations. Actions from different source profiles remain separate.

Repeated unfinished sessions for the same title on the same day can share a row. Open **Sessions** to see their times and progress. A new play after a completed watch gets its own row. This grouping changes only the activity display, not your watch history.

A normal **Stopped watching** result does not mean delivery failed. Check each destination in **Path**. A **Skipped** rating can mean the destination does not support episode ratings; supported destinations can still receive it. See [Plex rating support](https://wiki.crosswatch.app/crosswatch/settings/scrobbler/webhooks.md#rating-support-varies).

### Captures and backups

Select **Captures** for manual and scheduled provider captures, failures and retention cleanup. Select **Backups** for manual, scheduled and automatic backups, including copies to a backup destination. Managed users and monitor access cannot view Backups.

Choose **Successful** or **Failed** in the outcome filter, then open a record. Details show the trigger, provider/profile and feature for a capture, or the scope for a backup, plus available counts and failure explanations. **View logs** appears when a log session is available.

A backup can be saved locally even when copying it elsewhere fails; check both outcomes. Events contains the activity record, not the saved data. Use [Captures](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/captures.md) to inspect or restore provider data and [Backup & Restore](https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/backup-and-restore.md) for application backups.

Hub's **Recent Activity** shows failures and successful scheduled captures/backups. Successful manual operations and cleanup records remain available in Events; they do not all appear in that feed.

### Search and filters

Search by title, provider or reason. Results update as you type. In **Titles**, you can also type `from:plex` or `to:trakt`; CrossWatch turns these into source and destination filters. For example, `from:plex to:trakt` shows matching activity from Plex to Trakt.

Select **Filters** in the search bar for **When**, **Outcome**, **Review** and the other filters available in your view. Titles has separate **From** and **To** choices. Raw events offers event type, origin, feature and pair filters where applicable.

Filters apply immediately. Active chips stay visible in the search bar; remove a chip to clear that filter, or select **Clear all filters**. On mobile, **Done** closes the sheet.

Start with **Needs attention** and **Last 24 hours** when investigating a recent failure. Widen the range if the activity is missing. Titles, grouped activities and raw events show ten rows per page.

### Profile filter

Administrators can select **All profiles**, a named profile or **Admin**. The default-instance view limits events, statistics and calendar results to default provider instances and eligible pairs. Managed users remain within their assigned profile.

### Mark activity reviewed

Review status is separate from success or failure. **Any review status** is the default; choose **Unreviewed** or **Reviewed** to narrow the list.

In **Titles**, open a failed title and select **Mark reviewed**. Use **Reviewed** to undo it. Under **Needs attention**, **Mark all reviewed** marks failed destinations matching the current filters across the results, after confirmation. Check your filters first; this is not limited to the visible page.

In **Grouped** or **Raw events**, select individual checkboxes or **Select page**, then **Mark reviewed**. Select page covers only the current page, and changing pages clears the selection.

Reviewing only organizes Events. It does not retry or resolve a failure, clear pending sync items or change provider data.

### Raw events and linked threads

Use **Raw events** to inspect individual records and their order. Open a record for **Timeline**, **Details** and **Raw data**, including recorded reasons and available identifiers. Links from other pages may open a grouped thread directly.

**Current context**, when available, describes the item now. An old unresolved event can therefore show no current unresolved state. Use **View in Analyzer** for a current provider comparison.

For failed matches, **Possible matches** can show up to ten recorded candidates. These describe the earlier attempt, so check the destination before changing a mapping or retrying.

{% hint style="warning" %}
Raw data can contain provider names, identifiers and diagnostics. Review it before sharing it publicly.
{% endhint %}

### Statistics

Choose **Statistics**, then **24H**, **7D**, **30D** or **90D**. The initial range is 30 days.

The overview includes sync runs, watching, ratings, captures, backups and audits where your access permits. Activity trends count an activity once across destinations; **Top routes** counts each destination separately. **Skipped deliveries** is separate from failures.

Success rate excludes audits, skipped deliveries, stopped playback and work still in progress.

### Continue Watching hides

Continue Watching removal activity means hiding a title from a server's row while keeping its resume position. Check the destination result; an attempt alone does not confirm success.

See [Continue Watching removal sync](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/progress.md#sync-continue-watching-removals) for setup and Interactive Sync controls.

### Unknown watch dates

History skips can explain that a destination cannot preserve an unknown watch date or safely sync an undated rewatch. These are skipped outcomes, not completed writes. See [History date support](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history.md#unknown-watch-dates) before retrying.

### Refresh and clear

Select **Refresh** to reload activity while keeping your view and filters where possible. Use it after a sync completes.

Administrators can open **Filters → Clear archive** to delete all archived activity in the selected category after confirmation. Search and filters do not limit this deletion. Clearing Sync also removes its run summaries and calendar history; other categories remain.

{% hint style="danger" %}
Clear archive cannot be undone. It does not remove provider data, pair configuration or pending sync state.
{% endhint %}

New activity continues to be recorded after clearing.

### Troubleshooting

* **Titles are being prepared:** wait a moment and refresh. Older activity may need preparation when first opened after an upgrade.
* **No activity appears:** check the category and profile, clear filters, widen the date range and refresh. Older records may be incomplete or no longer retained.
* **A completed item is unreviewed:** review status is independent of the operation's outcome.
* **A failure needs investigation:** open its Path or recorded details, check current data in Analyzer, correct the cause and run the pair again. Confirm the later result before marking it reviewed.
* **The archive appears damaged:** use the Events health check in [Maintenance](https://wiki.crosswatch.app/crosswatch/settings/maintenance.md). Rebuild is a recovery action and cannot restore every historical run.

For a support request, include the affected title, route, result and relevant [logs](https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/logs.md). Remove private information before sharing.


---

# 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/tools/events.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.
