Feature Request: Ability to set expiration time on requests

[AstroGnouf]

IMO it would be really nice to be able to set a default expiration on requests. If your system has been running for years there's probably GOBS of requests that will just never be filled. So why not automatically clean them up so your system no longer burns cycles looking for them?

Ideally I'd like to see a setting where any new requests would expire in X number of days (completely user configurable) with the default being to never expire. Then to clean up old requests you could also run a job to say those expire from today in X number of days.

Because if the system can't find it in a year is it really going to find it in another year? Might as well save resources and automatically clean it out, if that user wants to try again they can try again.

Amazing work Team, thanks!

[fallenbagel]

So why not automatically clean them up so your system no longer burns cycles looking for them?

Not really how it works. Once a request is made, its handed over to sonarr/radarr. Seerr does nothing from then on. Deleting a request wouldn't do anything other than remove the record from seerr database.

[AstroGnouf]

I guess I'm coming from the cli_debrid world which polls Seerr for updates where this would be nice. I suppose if you're using The *Arrs it would't matter too much.

Gotcha though, thanks!

[fallenbagel]

I guess I'm coming from the cli_debrid world which polls Seerr for updates where this would be nice. I suppose if you're using The *Arrs it would't matter too much.

Gotcha though, thanks!

We don't officially support cli_debrid.

[AstroGnouf]

Fair enough. I appreciate you taking the time to respond.