Unuzable nzb/Failed URL is actually misleading for a "Wait x" common API msg

[Effenberg0x0]

sabnzbd+ fills history with one hundred "URL Fetching failed: Unuzable nzb file". Visiting the URL you see it actually is one of your search providers telling you your "API daily/hourly limit is reached, try again later".

- Deleting this items from history would confuse the nzb search program (like Sick Beard for example, which thinks the download was snatched)
- Most people won't look at the URL. Will simply delete, creating unnecessary search traffic to all news search providers again, while the nzb was perfectly good if the user would wait a little before trying again.
- Even trying again can be complicated. You have to manually click "try again" for many nzbs in your history. If they bounce back, it gets to a point in which you can't distinguish what has been tried again and what has not.

Someone smart at sabnzbd+ development must think of a better solution to this case and better management of the "try again".

How about this:

- The failed downloads / nzbs are referenced in the history as "API restriction" if the server response string contains "API", instead of "Unusable nzb or Failed URL", etc which are misleading.

- A list of "API Restricted" nzbs is created, like the one for "Orphaned" dloads.
- The list shows:


[More than 1 hour ago]
nzb1 - date/time
nzb2 - date/time
nzbn - date/time

[One day ago]
nzb1 - date/time
nzb2 - date/time
nzbn - date/time

[One week ago] -
nzb1 - date/time
nzb2 - date/time
nzbn - date/time


Anyway, its just a suggestion. You can probably imagine better ways to do it.

Regards,

[shypike]

If only nzbmatrix wasn't so foolish to send this message
instead of just telling how many minutes to wait.

[Effenberg0x0]

Yeah, nzbmatrix and nzb.su too. We know its not a 404, 500, etc error because there's content with the API and Error in the string. But that's it.
Both providers are absolutely defaults for Sick Beard users. All we can know is date/time when the download attempt failed. I think it could be archived that way in the sense of compatibility with future providers. Maybe instead of try again, something like "try again in one hour" (from the time when the error occurred). And every user is free to learn about its provider API, limitations, time-outs, etc, anyway. Its just important they know the NZB *is* valid.

[shypike]

Rather strange, currently SABnzbd does check for nzbmatrix's daily_limit error message.
So it should keep retrying.
Not extensively tested obviously, because with one account you can only test once per 24 hours.
I'll see what I can do.
So far nzb.su isn't really supported, because they have their own api, completely different from nzbmatrix and newzbin.