Scheduling
Control when and how often Huntarr hunts for your media.
Overview
- Each app and instance can have its own schedule
- Schedules control hunt frequency and item caps
- The scheduler runs independently for each configured task
How Scheduling Works
- Huntarr's scheduler engine checks all active schedules
- When a schedule's interval has elapsed, a hunt cycle begins
- The cycle processes up to the configured cap of items
- After completing, the scheduler waits for the next interval
Creating a Schedule
- Go to Settings > Scheduling
- Select an App Type (Sonarr, Radarr, Movie Hunt, etc.)
- Select an Instance (or Global for all instances)
- Set the schedule type (Interval or Cron)
- Configure the timing and caps
- Save
Schedule Settings
| Setting | Description |
|---|---|
| App Type | Which app this schedule controls |
| Instance | Specific instance or "Global" for all |
| Schedule Type | Interval (every N minutes) or Custom |
| Interval | Minutes between hunt cycles |
| Missing Cap | Max missing items to search per cycle |
| Upgrade Cap | Max items to upgrade per cycle |
| Enabled | Toggle this schedule on/off |
Recommended Settings
| App | Interval | Missing Cap | Upgrade Cap | Notes |
|---|---|---|---|---|
| Sonarr | 30 min | 5 | 3 | Episodes search quickly |
| Radarr | 60 min | 3 | 2 | Movies take longer to find |
| Lidarr | 60 min | 3 | 2 | Music indexers can be slow |
| Movie Hunt | 30 min | 5 | 3 | Uses own indexers |
Tips
- Start conservative and increase caps gradually
- Too-aggressive schedules may trigger indexer rate limits
- Use per-instance schedules to stagger load across instances
- Global schedules apply to all instances of that app type
- Check the Hunt Manager for schedule execution history
Rate limits
Setting very low intervals (under 15 minutes) with high caps may cause indexer bans. Start with 30-minute intervals.