Check media availability before Jellyfin cleanup tasks

The useful distinctions

• Scheduled tasks can be run manually with their run button.
• The collections-and-playlists cleanup can remove playlist content when media is unavailable.
• That cleanup is documented as running at startup by default.
• Plugins can contribute additional scheduled tasks.

Separate a missing disk from missing media

A temporary storage outage does not necessarily mean the owner intentionally removed the files. That distinction matters when a maintenance job reconciles catalogue references against what the server can see. Before starting cleanup, inspect a few known items from each source location. A successful check on one volume is not evidence that every path used by a playlist is present.

Review triggers before a restart

The important question is when a task runs, not only whether someone pressed its button. Keep a short maintenance note that connects each sensitive task to the storage it depends on. The synthetic checklist below uses two fictional volumes and a playlist spanning both. It makes an otherwise invisible dependency visible before a routine server restart turns into an unexpected catalogue change.

Preserve the evidence of intent

If media is intentionally retired, write that down separately from an availability incident. Record task names, trigger choices and whether the folders were reachable when an unwanted change occurred. This gives a support investigation a useful sequence of events. Repeated scans without understanding that sequence can produce more activity while leaving the original reason for lost membership unresolved in the administrator’s notes.

A focused way to proceed

1. Open the scheduled-task list and identify collection/playlist cleanup and its trigger.
2. Check that the source media folders are available to the server before running maintenance.
3. Review plugin-added tasks as well as the built-in list.
4. Run only the intended task and inspect its result before restarting or scheduling further cleanup.

Worked example · synthetic

Maintenance gate:
/media/films-a: available
/media/films-b: unavailable
Playlist: Workshop Evening uses both
Decision: restore storage visibility before collection/playlist cleanup

Read the comparison

An unavailable source is a reason to investigate the dependency before cleanup, not proof of deliberate media deletion.

When to stop or ask for help

If membership was lost, preserve logs and backups and review recovery options before more maintenance changes.