Jellyfin Tasks
The media server’s scheduled tasks: when each last ran, how long it took against its usual time, and when it runs next.
About this page
A duration creeping past 3× its own median is the early warning that the library is outgrowing the hardware. The row is marked, and the line at the top of the page names it.
Stock Jellyfin keeps no task history, so the durations, the median and the last eight runs are the panel’s own record of the runs it has seen.
The heavy tasks (trickplay, chapter images, Intro Skipper, audio normalisation, keyframes) have no Jellyfin schedule: the panel runs them one at a time after the 3:00 am scan, only while nobody but Kev is watching, and stops one if somebody starts. Every other task runs on Jellyfin’s timer at the time the panel keeps for it; Schedules lists them all, with every machine’s timers.
Run on Scan Media Library asks what to scan first: usually every film and show library one at a time, which takes minutes. Music and the full scan take hours.
A task that failed shows up twice: as a red row here, and a few seconds later as a line on Jellyfin Logs. The reason it failed is only ever in the log, which is why a failed row links there.