Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
I've a SAB category named "tv" with a priority of 'high'.
Since upgrading to 2.3.0 from 2.2.1, the NZBs received from SickRage are being correctly assigned to the "tv" category in SAB, but are being set to 'normal' priority.
The following debug line may not be relevant but thought I'd include it anyway:
If sickrage includes in the url a priority=x parameter, this overrules the category setting. Is that maybe the case? You should be able to see the API add command in the logs to. What does it look like?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Confirmed: downloaded the updated nzbstuff.py into my master installation, sent an episode from SickRage to SAB and it is now assigned the correct priority.
Just found the same problem occurs during a manual 'add'.
SABnzbd 2.3.0
Via the SAB GUI, I browsed to my ZIP file (containing a couple of NZBs), selected the required category, left all the other options as 'default' (post processing, priority, script), clicked 'Add', then found the NZBs are in the download queue in the correct category, but with 'normal' priority.