You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Webhook jobs and Recently Added sweeps now jump the queue. New media from Sonarr/Radarr/Plex/Emby/Jellyfin runs at High priority by default, so a fresh import overtakes a running full-library regeneration instead of queueing behind the rest of it. It cuts in file-by-file — the scan keeps its slot and keeps running, it just stops being fed new files until your new episode is done. Configurable under Settings → Processing Options → Job Execution → Incoming job priority.
One concurrency slot is held back for high-priority work whenever Max concurrent jobs is above 1, so an incoming webhook never has to wait out a queue full of multi-hour scans. Trade-off worth knowing: normal-priority jobs get one slot fewer (2 of 3 at the default cap). Raise the cap by 1 if you want the old throughput.
Schedules have a new "Default (from Settings)" priority option, now the default for new schedules. Existing Recently Added schedules have an explicit Normal saved on them — edit the schedule and set Job Priority to Default (from Settings) to pick up the new behaviour.
Fixes
The job-priority tooltips said a running job isn't affected by a higher-priority new job. It is — priority reassigns workers file-by-file, without cancelling or pausing anything. Wording corrected.