Fixing a stuck import without opening a laptop

Everything downloaded fine. The file is on disk. And yet the show still says missing, the queue is jammed, and nothing moved into your library. Stuck imports are the single most common "why is this not working" in a media stack, and almost all of them come down to the same short list. Here is the order I check.

Start at the download client

Before blaming anything clever, confirm the download actually completed and is sitting where it should. A torrent still seeding at zero percent, or a Usenet download that failed its repair, will look done from a distance and is not.

• Is the download at 100 percent and marked complete?
• Is it in the category or folder your arr app expects?
• Did it actually finish, or fail extraction quietly?

Then check the category and paths

This is where most of them die. The arr app watches a specific completed folder, sorted by a specific category. If the download client dropped the file somewhere else, the import never triggers.

• The category in the download client must match what Sonarr or Radarr expects.
• The completed path the client writes to must be a path the arr app can actually see, with the same mapping if you run containers.
• Remote path mappings are the usual culprit when the two run on different machines.

Then permissions and disk

If the paths line up and it still will not move, it is usually the boring stuff.

• The user your arr app runs as needs read and write on both the source and the destination.
• A full disk stops an import cold, and the error is not always loud about it.

Then the release itself

Sometimes the file is just not what the app wanted.

• The release did not match, so the app does not trust that it belongs to that movie or episode.
• A weird nested folder or an odd naming scheme confused the parser.
• A manual import, where you pick the file and tell the app what it is, clears these fast.

The point is the order

Stuck imports feel maddening because people check the hard things first. Work the chain in order instead: client, category, paths, permissions, disk, release. Nine times out of ten you find it in the first three, and you can do the whole check from your phone without ever sitting down at a desk.