SSD Nodes Learn Hosting plans →
Guides Matt ConnorBy Matt Connor

Fix Sonarr or Radarr stuck on Waiting to Import

Your download finished but never reached the library. Find the reason in the queue and the Trace log, then fix paths, permissions, archives or categories.

Why Sonarr or Radarr is stuck on Waiting to Import

Sonarr or Radarr stuck on Waiting to Import means the download finished, but the import into your library did not happen. The app nearly always records the reason. Hover over the status icon in Activity > Queue, then read the log file at Trace level. In most cases the cause is one of five things, and this guide checks them in the order they usually turn out to be the problem.

The behavior below matches Sonarr v4. As of 21 November 2026 the latest stable Sonarr release on GitHub is v4.0.20.3014, and the 5.0.0 builds are marked pre-release. The latest stable Radarr release is v7.0.3.10918. If you run the LinuxServer.io image on its develop tag, note that its changelog moved that branch to Sonarr v5 in October 2026, so some labels may differ for you.

What the queue status labels mean

A completed download in Sonarr v4 shows one of these labels in Activity > Queue. They come from the Sonarr frontend source:

  • Downloaded - Waiting to Import
  • Downloaded - Unable to Import Automatically
  • Downloaded - Importing
  • Downloaded - Waiting to Process

Any queue error on a completed item shows as Import Failed: followed by the release name. Radarr's wiki lists the same Downloaded - ... labels for Radarr, plus Warning, Download Failed and Import Failed.

The two labels that bring people here are the first two. Both say the same thing: the file is on disk, and the app has not moved it into your library. The label does not tell you why. The tooltip does.

Where to find the reason for a stuck import

Start with the queue. The Servarr wiki says import problems show as an item in Activity with a warning icon that you can hover over to see the error. The number badge next to Activity uses yellow for a warning and red for an error. Hover over the icon on the stuck row and read the full text. Write it down, because the cause sections below are matched to that text.

If the tooltip is vague, turn on Trace logging. The wiki names this as the first debugging step.

  1. Open Settings > General and set Log Level to Trace.
  2. Wait a minute or two, so the app checks its download clients again.
  3. Open System > Logs > Files and download the newest trace file.

Sonarr writes sonarr.trace.txt files and keeps up to 51 of them in rotation. Radarr writes radarr.trace.txt. Do not rely on the Events table in the UI. The wiki says it is not the same as the log files and is less useful. Search the trace file for the release name, then read the lines around it. Set the log level back to Info when you are done, because Trace writes a lot.

Cause 1: the download client reports a path Sonarr cannot see

This is the most common cause on a Docker setup. The log line looks like this:

Import failed, path does not exist or is not accessible by Sonarr: /downloads/tv/Show.Name.S01E01.1080p

Radarr writes the same line ending in by Radarr:. Sonarr may also raise a health warning that reads Sonarr failed to import (an) episode(s). Check your logs for details.

Here is the mechanism. When a download finishes, the download client tells Sonarr where it saved the file. It reports the path as it sees it, inside its own container. Sonarr then looks for that exact path inside the Sonarr container. If the two containers mount the same host folder at different paths, the path string does not exist on Sonarr's side, so the import stops.

A typical broken compose file mounts the folders like this:

services:
  qbittorrent:
    volumes:
      - /srv/data/torrents:/downloads
  sonarr:
    volumes:
      - /srv/data/media/tv:/tv
      - /srv/data/torrents:/data/torrents

qBittorrent saves to /downloads/tv/.... Sonarr has the same files, but at /data/torrents/tv/.... Confirm it by asking the Sonarr container for the exact path from the log line:

docker exec sonarr ls -la "/downloads/tv/Show.Name.S01E01.1080p"

An ls: cannot access error ending in No such file or directory confirms the mismatch. Replace sonarr with your container name if it differs. docker ps lists them.

Fix the mounts, not the symptom

The Servarr wiki is direct about this. If both the *arr and the download client are Docker containers, a remote path map is rarely needed, and on Docker fixing the paths is the better option. The Servarr Docker guide asks for one unified set of paths across all containers. Sonarr, Radarr and Lidarr each get one /data mount, and the download client sees the same paths below it:

services:
  qbittorrent:
    volumes:
      - /srv/data/torrents:/data/torrents
  sonarr:
    volumes:
      - /srv/data:/data

Then set the save path inside the download client to /data/torrents/tv, or to a category folder below /data/torrents. The path it reports then exists in both containers. Recreate the containers with docker compose up -d. A plain docker compose restart keeps the old mounts, which is explained in when to restart a Compose service and when to recreate it. Check again:

docker exec sonarr ls -la /data/torrents/tv

You should see the finished download. Point the root folder in Sonarr at /data/media/tv, and the download and the library sit on one mount. The Docker guide says this lets hard links work and makes moves atomic. Separate mounts such as /tv and /downloads look like different file systems to the app. Hard links then do not work, and a slower copy plus delete is used instead. The LinuxServer.io docs say the same about their optional /tv and /downloads paths: the main cost is losing the ability to hardlink. A full example stack with this layout is in the Docker Compose file for the arr stack.

When a Remote Path Mapping is the right fix

Remote Path Mappings live in Settings > Download Clients. The wiki calls a mapping a dumb find and replace: for a given Host, it finds the Remote Path and replaces it with the Local Path. Use one when you do not control the other side, such as a seedbox. Use one also when the download client and Sonarr run on different operating systems, Linux on one side and Windows on the other. Check the exact field labels in your own UI.

The wiki gives one useful test. If the path in the error message does not contain your replaced value, the mapping is not being applied. Check that the Host in the mapping is the same host you entered for the download client.

Cause 2: permissions, PUID, PGID and umask

The wiki says most import errors are permissions issues. The user or group that Sonarr runs as must be able to read and write the downloaded files. It must also be able to write to the library folder.

The LinuxServer.io images take PUID and PGID variables. These map the user inside the container to a user on the host. If qBittorrent runs as one user and Sonarr as another, Sonarr can end up with files it can read but not move or delete. The full explanation is in Docker PUID and PGID explained.

To confirm, compare what each container runs as with who owns the files on the host:

docker compose config | grep -E 'PUID|PGID|UMASK'
ls -ln /srv/data/torrents/tv
ls -ln /srv/data/media/tv

ls -ln prints numeric owners, so you can compare them with the PUID and PGID values directly. Say the files are owned by 1001 1001 with mode -rw-r--r--, and Sonarr runs with PUID=1000 and PGID=1000. Sonarr can read those files but cannot write to them.

The Servarr Docker guide recommends one of two setups. The first is a shared group with a umask of 002, which gives folders 775 and files 664. The simpler second setup is a single shared user with a umask of 022, which gives 755 and 644. Never use 000. The LinuxServer.io docs show UMASK=022 as an optional setting. Do not read that as a default, because their example compose files have no UMASK line at all.

If every container uses the same PUID and PGID (here 1000), fix the existing files once:

sudo chown -R 1000:1000 /srv/data
sudo find /srv/data -type d -exec chmod 775 {} +
sudo find /srv/data -type f -exec chmod 664 {} +

Use your own IDs if they are not 1000. Then watch the queue item again.

Two more points from the wiki. Settings > Media Management > Set Permissions runs chmod on import, but it only works if the user running Sonarr owns the file. The wiki says it is better to make the download client set permissions properly. On network storage, an NFS mount needs nolock, and an SMB mount needs nobrl.

Cause 3: the release does not match a series or episode

Sometimes the file is readable and in the right place, but Sonarr cannot decide which episode it is. The tooltip then names a matching problem instead of a path. Mislabeled releases and odd numbering both end here. The wiki's fix is Manual Import: click the human icon on the right of the queue row in Activity > Queue. In the dialog, pick the series and the episode for each file, then import. If the release was mislabeled, the wiki asks you to report it to your indexer.

Some warnings mention a match found through grab history. Radarr's FAQ explains that in this case you must confirm it is the right title and import it by hand. Read the exact text in your own tooltip, because the wording differs between Sonarr and Radarr.

Releases that cannot be parsed at all still show in the queue, because Activity > Options > Show Unknown is enabled by default in recent builds. If you switched it off, switch it back on. It lists items in the app's download client category that were not otherwise ignored or imported. The wiki says these usually need to be mapped and imported by hand.

Anime and fan edits

Anime is the most common case. Check the series type on the series first. The Sonarr FAQ says Anime is usually right, but Standard sometimes works better. The Anime type has no concept of season packs or seasons. Two strings point at numbering problems:

Episode does not have an absolute episode number
Numbering varies for this episode and release does not match any known mappings.

The first means the episodes on TVDb have no absolute number assigned. The second means the scene numbering of the release does not match a known mapping. The FAQ says XEM is the only way to fix Japanese anime aliases. For scene numbering problems, it says you need to grab and import the episodes by hand.

Fan edits such as One Pace re-cut the original episodes, so their file names do not follow the episode list Sonarr knows. Treat them the same way: Manual Import each file and pick the episode yourself. That is the wiki's general advice for unmatched releases. It does not give a separate recipe for fan edits.

Cause 4: the download is an archive that was never extracted

Torrents packed in .rar files are the classic case. Sonarr's import service has no extraction step in the source code I read. When a download folder holds no video file but does hold an archive, Sonarr rejects it with this reason:

Found archive file, might need to be extracted

A single archive file on its own can instead be rejected as Invalid video file, unsupported extension: '.rar'. For a folder with a .rar larger than 10 MB, the log adds RAR file detected, will require manual cleanup. The extensions Sonarr treats as archives include .rar, .r00, .zip, .7z, .tar and .gz. To confirm, list the download folder:

ls -la /srv/data/torrents/tv/Show.Name.S01E01.1080p

A folder of .rar and .r00 files with no .mkv confirms it. The Servarr wiki says that if a torrent is packed in .rar files you must set up extraction. It recommends Unpackerr for this, because it prevents corrupt partial imports. The Sonarr FAQ notes that most torrent clients lack the automatic archive handling that usenet clients have, which is why this mostly affects torrents. The Radarr troubleshooting page gives the same advice for Radarr.

Cause 5: Completed Download Handling or the category is wrong

Completed Download Handling is how Sonarr imports media from your download client into your series folders. It lives in Settings > Download Clients. Its Enable option is an advanced global setting, described as "Automatically import completed downloads from the download client". Show the advanced settings if you do not see it, and make sure it is on.

Next, check the category. The wiki says Sonarr should use a category in the download client, so that it only tries to process its own downloads. The queue only shows items in that category. A download sent without the category, or moved to another category by a rule in the client, never reaches the import. You can set the category at any time. How to set it per client is in connecting Prowlarr, Sonarr and Radarr to a download client.

Also check what removes finished downloads. The wiki says the download client should not be the one removing them. If the client deletes a torrent as soon as it completes, the files can be gone before the import runs. The per-client Remove Completed option in Sonarr is the right place for cleanup. For torrents, it needs the client to pause the torrent when it reaches its seed goals.

Last, the download folder and the library folder must be separate. The wiki says you should never download directly into your root folder. If they are the same folder, or the folder holds no valid media file, the log shows:

No files found are eligible for import

Prevent it with one folder layout

Most of these causes come from the folder layout, not from Sonarr. A single /data tree mounted the same way in every container removes cause 1. Shared IDs with a umask of 002 remove most of cause 2. The layout, with hard links and the exact folder names, is in the arr stack folder structure and hardlinks guide. Set it up once and the queue stops filling with items stuck on Waiting to Import.

FAQ

What does "Downloaded - Waiting to Import" mean in Sonarr?

It means the download client finished the download, but Sonarr has not moved the file into your library yet. If it stays there for more than a few minutes, something is blocking the import. Hover over the status icon in Activity > Queue to read the reason. If the tooltip is unclear, set Settings > General > Log Level to Trace and read the newest trace file under System > Logs > Files.

Do I need a Remote Path Mapping if Sonarr and qBittorrent both run in Docker?

Almost never. The Servarr wiki says that when both apps are Docker containers a remote path map is rarely needed, and that fixing the paths is the better option. Mount the same host folder at the same path in both containers, for example /data/torrents, and set the client's save path to match. Keep Remote Path Mappings for a seedbox or for a client on a different operating system.

Does Sonarr extract RAR files?

Sonarr's import service has no extraction step in its source code. A folder with an archive and no video file is rejected with Found archive file, might need to be extracted. The Servarr wiki says you must set up extraction for .rar torrents and recommends Unpackerr. Most torrent clients do not unpack archives the way usenet clients do, so this mostly affects torrents.

Why will Sonarr not import my anime or One Pace episodes automatically?

Sonarr could not match the files to episodes it knows. For anime, check the series type first: Anime is usually right, but Standard sometimes works better. Missing absolute numbers on TVDb and scene numbering that does not match a known mapping both stop automatic imports. Fan edits such as One Pace do not follow the original episode list. In all these cases, use Manual Import (the human icon in Activity > Queue) and pick each episode yourself.

Was this article useful?