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

# Scheduling

Configure standard recurring syncs and advanced plans with timed steps, automated captures, and event triggers.

Enable periodic runs in **Settings → Scheduling**.

### Standard scheduling

Use this for simple recurring syncs.

It applies one cadence to enabled pairs that do not have an active Profile schedule.

Turn on **Use standard plan** to enable the recurring schedule.

Instead of showing every timing field at once, it works in two steps:

1. Choose a frequency.
2. Fill in the one extra timing field that matches that choice.

This keeps irrelevant inputs off the screen.

#### Current plan

The top of the wizard shows a live **Current plan** summary.

It updates as you change the schedule.

Use it to confirm the schedule in plain language before saving.

#### Frequency options

**Every hour**

Runs once at the top of every hour.

No extra timing field is needed.

**Every N hours**

Runs on a repeating hour-based interval.

Set how many hours to wait between runs.

Use this when hourly is too frequent, but once per day is too slow.

**Daily at**

Runs once per day at a specific local time.

Set a time like `03:30`.

**Custom**

Runs on a custom repeat interval in minutes or hours.

Use this when the built-in hourly or daily options do not fit.

#### Custom schedule rules

* Minimum interval: `15 minutes`
* Units: `minutes` or `hours`
* Intervals under `1 hour` show a warning in the UI

{% hint style="warning" %}
Intervals shorter than `1 hour` can look like aggressive polling to provider APIs.

That may be treated as API abuse and can risk throttling or a ban.
{% endhint %}

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FnoM1zpe79AlI9WxWKDQd%2Fimage.png?alt=media&amp;token=b88f9204-ec24-437d-8c11-7e8c0d83c4fa" alt=""><figcaption></figcaption></figure>

#### Recommendation

Start with **Daily at** for most setups.

Use **Every N hours** when you need a shorter repeat window.

{% hint style="info" %}
Add an Advanced plan when you need per-pair times, captures, or event triggers. You can keep the Standard plan enabled.
{% endhint %}

### Advanced scheduling

Use **Use advanced plan** when one recurring schedule is insufficient.

The Standard and Advanced plans have independent switches. Enabling or saving one does not disable the other.

It combines timed sync steps, scheduled captures, and event triggers.

The advanced plan and [Scheduler Webhooks](https://wiki.crosswatch.app/crosswatch/settings/scheduling/scheduler-webhooks.md) are administrator-only.

#### Current plan

The advanced panel shows a live **Current plan** summary.

It lists timed steps, capture schedules, and event triggers.

It also reports whether the plan is active, ready, or needs attention. If steps are configured but **Use advanced plan** is off, it shows **Not running, advanced plan is off**. Configured steps do not run until that switch is enabled.

Specific warnings identify the affected section.

Examples include `Timed steps need attention` and `Event triggers need attention`.

#### Time plan

Use the Time Plan for per-pair timing and ordered runs.

Each row configures one sync step:

* **Pair** — an enabled pair to run. The picker shows the provider accounts, sync direction, and enabled features. **Disabled** pairs cannot be selected. **No features** identifies a pair with nothing enabled; configure its features before using it. A **Step** label shows where the pair is already used in the plan.
* **Time** — the local 24-hour start time.
* **Days** — weekdays when the step can run.
* **After** — another step that must finish first.
* **Active** — enable or pause the step.

When **After** is set, CrossWatch ignores the step’s time.

Steps run from top to bottom and never run in parallel.

List order decides ties between steps with the same time.

Use **Auto-create from enabled pairs** to create a starter plan.

#### Capture schedules

Capture Schedules create provider restore points on a schedule.

They run separately from sync jobs.

Each row selects:

* **Provider**, **Profile**, and **Feature** to capture.
* **Time** and **Days** for the capture.
* **Active** to enable or pause the schedule.

The feature can be watchlist, ratings, history, progress, or all.

Advanced options control capture names and retention:

* **Label template** supports `{provider}`, `{instance}`, `{feature}`, `{date}`, `{time}`, `{datetime}`, and `{stamp}`.
* **Keep captures for days** removes captures older than the chosen age.
* **Max captures to keep** limits retained captures by count.
* **Cleanup** applies retention after a successful scheduled capture.

When **Cleanup** is off, CrossWatch does not automatically delete captures.

When both retention limits are set, both rules apply.

See [Captures](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/captures.md) for restore and comparison workflows.

#### Event triggers

Event Triggers run a sync pair after watcher or webhook activity.

Filter triggers by event type, media type, progress, or route.

Use guardrails to prevent excessive runs:

* **Mute (min)** ignores new triggers after a run starts.
* **Dedupe (sec)** suppresses identical repeated events.
* **Max / hour** caps each rule’s hourly runs.

See [Watcher](https://wiki.crosswatch.app/crosswatch/settings/scrobbler/watcher.md) and [Webhooks](https://wiki.crosswatch.app/crosswatch/settings/scrobbler/webhooks.md) for event sources.

### Running plans together

Enable **Use standard plan** and **Use advanced plan** to use both. For example, keep a daily Standard run and add Advanced times for selected pairs.

Sync runs execute one at a time. When both plans are due together, Advanced work runs first and the Standard run skips pairs already accepted for execution by that Advanced occurrence. If every eligible pair has already started, no extra Standard run is needed. Runs scheduled for different times remain separate; overlap handling does not prevent a later scheduled run.

[Scheduled backups](https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/backup-and-restore.md#schedule-backups) use their own enable setting and can run with both plans off. Disabling Advanced does not disable backups; open **Tools → Backup & Restore → Schedule & storage → Automatic backups → Edit schedule** and turn off **Back up automatically** if needed.

### Profile schedules

**Profile schedules** lists one schedule for each Profile.

Open the Profile in **Profile schedules** and enable **Run \[profile name]'s pairs on their own schedule**. Under **Frequency**, choose **Every hour**, **Every few hours**, **Once a day**, or **Custom interval**. Fill in the displayed hours, time, or interval field, then select **Save schedule**. Custom intervals must be at least 60 minutes.

While a Profile schedule is on, the global standard schedule skips that Profile's pairs.

A signed-in user with the **Schedule** grant sees and edits only their own Profile schedule.

See [Profiles](https://wiki.crosswatch.app/crosswatch/settings/connections/profiles.md) for Profile scope and access.

### Which mode to use

* Use **Standard Scheduling** for simple recurring syncs.
* Use **Advanced Scheduling** when you need multiple jobs, captures, event-driven behavior, or a more structured automation workflow.
* Enable both when you want a general cadence plus targeted runs.

### Scheduler Webhooks

Send scheduled sync start, success, and failure events to an external service.

See [Scheduler Webhooks](https://wiki.crosswatch.app/crosswatch/settings/scheduling/scheduler-webhooks.md) for setup and configuration details.


---

# 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/scheduling.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.
