I think they did not understand you.
If I'm not mistaken (I don't use Sonarr so I may be wrong): when Sonarr sends a nzb to nzbget it then periodically checks the nzb status in nzbget history. When it sees status FAILURE or SUCCESS it handles it correctly. But when it sees status "BAD" or "DELETED" it does nothing. Since the item landed in nzbget history it's done. I would expect Sonarr to handle anything that is not SUCCESS as failure.
Regardless, the status "BAD" must be treat as "FAILURE" without doubts. I cannot add new command "Mark as failure" because existing command "Mark as bad" does exactly that. Take a look at field status as it is represented via
API (only few statuses shown, click on link for more info):
Code: Select all
SUCCESS/HEALTH
SUCCESS/GOOD
FAILURE/PAR
FAILURE/UNPACK
FAILURE/MOVE
FAILURE/HEALTH
FAILURE/BAD
...etc
As you see there many statuses representing failure. All statuses starting with "FAILURE" must be treat as failure. Why would Sonarr have a special processing (ignoring) for status "FAILURE/BAD"? Are you sure it doesn't handle it?