Support Forum

Do you have Sorting enabled in sabnzbd? Just check to be sure. Otherwise sabnzbd unpacks the folder exactly as it was told, in a folder with the same name as the job. How have you setup sabnzbd in Sonarr? Using the API key? This way sonarr should keep internally track of which folder to use by calli...

I think this probably is setup somewhere in that software? We don't include any links to it
It's a macOS app, so no reasons why it should link to that.
Maybe a simple restart will do the trick?

Did you do any diagnostics yourself?
For example when you go into all of these programs, what happens if you test the connection to sabnzbd from within these programs?
Have you restarted your computer?
What do you have set for Hostname in sabnzbd?

We thought about that, it's indeed been on the request list. Haven't been completely sure how to implement it nicely.
Glitter supports drag-and-drop of jobs to arrange queue, but that's limited to current queue page indeed.

Smpl is not supported anymore. It's mega ancient.
Only Glitter is fully supported, Plush is only legacy supported.

You have to be a bit more specific, who is not processing it?
Sonarr? Radarr? Sickrage?

This error is thrown by sabnzbd when the disk system tells us we cannot write to it. It can be a permissions issue or maybe something went wrong with the folders?
The folder it's trying to write to, it exists and is writable for the sabnzbd user?

I have not had time to inspect the logs, I will get to it, not forgotten.

2.2.0 Multipar came, so 2 months ago.
But you probably also have 'Post-process only verified jobs' turned off, otherwise all these jobs would have shown in your history with this error and SAB would not have tried to unpack.

We switched from par2cmdline to Multipar (much faster), so old parameters didn't work anymore. That's why we made the warning

In retrospect we should have removed all custom par2 parameters during the upgrade, but we forgot..

Is any verification and repair happening? Because it sounds like you have missing pieces that should be repaired. Unless you are downloading from a source that provides NZBs without par2? You can enable Debug logging in the Status window and then you can see in the logging what happend with the veri...

Can you try sabnzbd 2.3.1RC1? It seems like you maybe have a path with a special character, which should be handled better in 2.3.1.

Do you want to run a script?
This can only have been set by the user. Scripts don't just run, try checking the Config Categories page.
Or, try in Config Notifications if you maybe selected the script as a Notification script?

Yes somebody should make new version but takes effort to maintain, these special Download NZB buttons for all indexers in particular.

You can have the folder anywhere, just have to set up the correct path.