> 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
Enable periodic runs in **Settings → Scheduling**.
{% hint style="success" %}
Most installs should start with one daily schedule.
{% endhint %}
### Standard scheduling
Use this for simple recurring syncs.
It applies one cadence to all enabled pairs.
The new Standard Scheduler replaces the old basic scheduler with a guided wizard.
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 %}
#### Recommendation
Start with **Daily at** for most setups.
Use **Every N hours** when you need a shorter repeat window.
{% hint style="info" %}
Move to Advanced Scheduling only when one repeating schedule is no longer enough.
{% endhint %}
### Advanced scheduling
Use **Use advanced plan** when one recurring schedule is insufficient.
An advanced plan replaces the standard cadence.
It combines timed sync steps, scheduled captures, and event triggers.
#### 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.
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.
* **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](/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](/crosswatch/settings/scrobbler/watcher.md) and [Webhooks](/crosswatch/settings/scrobbler/webhooks.md) for event sources.
### 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.
---
# 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/crosswatch/settings/scheduling.md?ask=&goal=
```
`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.