Compare one completed file in one library
Choose one authorised file that has finished being copied into the intended library location. Record its arrival time and whether it is initially absent from the library. Ask the operator to run the appropriate scan and retain the completion result, rather than moving an entire collection between folders.
For an illustrative network-storage setup, a new episode is absent before the scan and appears afterwards. That observation supports investigating automatic detection. It does not establish that every folder has correct permissions or that another partly copied file should already have been listed.
Check the server’s library path
Jellyfin libraries can combine several server paths into one displayed collection. The title of a library therefore does not uniquely identify a storage folder. Confirm which configured path contains the new item and whether that path is available in the actual server environment.
If a scan also fails to find the item, keep that different result. The next investigation includes the selected path, suitable library content type and file organisation. Do not diagnose a change-notification limitation merely because a client’s list has not refreshed; first establish that the server’s own scan can discover the item.
Review automatic monitoring support
Jellyfin documents that real-time monitoring depends on the filesystem. Its Linux guidance uses inotify and explicitly identifies NFS and rclone as lacking that notification support. The page also describes watch-limit errors for large libraries. Check the relevant environment and log message rather than applying one workaround to every server.
For example, a storage backend without the needed notifications and a local filesystem that has exhausted its watch allocation need different operator decisions. Reinstalling the television client does not change either server-side condition. Preserve the successful scan as evidence while the operator chooses an appropriate supported update strategy.
Choose a repeatable update workflow
Agree how new material should be detected on this installation and how long the household should normally expect an update to take. Use a deliberate scan where appropriate while the operator reviews automatic monitoring. Do not invent an immediate-update promise or repeatedly rename working media to force a visible change.
Verify the chosen workflow with another completed, permitted file in the same path and retain its arrival and discovery times. A useful report includes the storage type, relevant library path context, scan result and any watcher error, with private names removed. It distinguishes access, discovery and automatic notification without claiming a benchmarked server.
Questions about this guide
If a manual scan finds the file, is the missing item necessarily a client installation problem?
No. Investigate the server’s automatic change-notification path as well.
Does Jellyfin promise real-time monitoring on every filesystem?
No. Its troubleshooting guidance explicitly limits filesystem support.