[Suggestion] Graceful degradation when TorBox is unreachable

[Ventrex]

When TorBox has an outage or is temporarily rate-limiting, the current retry queue retries on failed hashes, but a full platform-unavailability scenario isn't explicitly handled (when I ready the docs correctly) the scheduler job just fails and won't retry until the next scheduled run.

Suggestion: When a TorBox API call fails with a network/5xx error (not a bad hash), queue the entire request and immediately retry as soon as the next successful health check comes in, rather than waiting for the next scheduler tick. This way a 10-minute TorBox hiccup doesn't cause a 6-hour delay.

[corveck79]

Was a bug, its fixed. TorBox outage no longer causes 6-hour retry delay for affected items