SABnzbd Forums

Feature: When changing provider API key on config, parse/update URLs of jobs in history that are failed. (Probably at queue too?).

Why?
- You have failed jobs in your history that you waited a couple hours / day to try again (daily limit, etc). You know they are valid anyway.
- Meanwhile you were asked / forced, whatever to change your API key with the search provider
- You hit try again, but now the jobs in history really became invalid (invalid login information)
- You can't request your old API key back to provider. Its lost.
- A new search is needed. Manually update status on Sick Beard from snatched to wanted, etc.

Thanks,
Effenberg

The next 0.6.0 Beta will not send NZB to history because of indexer limits.
Other than that, the use case is rather thin.

>>The next 0.6.0 Beta will not send NZB to history because of indexer limits
That would make everything easier, thank you.

>> thin.
Maybe. But imagine that, eventually, the need for API change happens. Errors in the providers are actually making it more frequent. There's a great chance the users will have something in their queues or history using the old API still to be processed, which would then certainly fail. So far, best workaround is to grep/sed whatever the old for the new API, which is not really obvious for the average user. If possible and not too much work, I would consider for the future (low priority obviously).

Thanks,