# Scheduling

Enabled repos run automatically on a schedule you set. The scheduler sweeps
every ~10 minutes and triggers runs for repos whose window matches.

## Settings

| Setting | Meaning |
|---|---|
| **Schedule days** | Days of week the repo may run (Mon–Sun) |
| **Start / end hour** | The daily window, e.g. 9–18 |
| **Spawn interval** | Minimum minutes between runs (cooldown), floored at 10 |

> **Time zone.** Schedule hours are **Europe/Paris**, so "9" means 9 AM Paris —
> not UTC. Overnight windows (e.g. 22→6) are supported.

> **Multiple features?** See [Scheduler priority](/docs/scheduler-priority) for how
> explore mode, issue solving, PR watcher, and issue scout are prioritised when
> several are enabled on the same repo.

## Rules a repo must satisfy to fire

1. `enabled` is true (not paused).
2. The current day + hour fall in the schedule window.
3. No run is already active for the repo.
4. The account's daily run limit isn't exhausted ([plan limits](/docs/plans-and-limits)).
5. The last run finished at least *spawn interval* minutes ago (cooldown).
6. The objective isn't already [met](/docs/objectives).

## Manual runs

You can always click **Run** to trigger immediately, regardless of schedule or
pause state (subject to the daily limit).

## Run isolation

Each run is independent: the panel keeps **no working tree** and pins no commit —
it sends only your repo URL, and the worker **fresh‑clones the current default
branch** every run. So a run always starts from whatever is on `main`/`master`
right now, including any [auto‑merged](/docs/auto-merge) PR from a previous run. A
failed or interrupted run leaves no residue for the next one to inherit. (To
instead *continue* an open PR, see [recovering a PR](/docs/recovering-a-pr).)

## Related

- [Scheduler priority](/docs/scheduler-priority)
- [Auto-merge](/docs/auto-merge) · [Recovering a PR](/docs/recovering-a-pr)
- [Objectives](/docs/objectives) · [Explore mode](/docs/explore-mode)
- [Plans & limits](/docs/plans-and-limits)