Silent Request Failures Leave Media in Invalid 'Requested' State

[marchershey]

Before I get into this, I just want to say I'm fully aware that my setup is a bit janky, so please ignore that part, and follow through with this request to save me from myself. lol

Long story short, I’ve got Radarr and Sonarr running through a separate VPN container, and every so often that VPN drops unexpectedly. When it does, it takes both services offline (usually due to health checks) until I catch it and resolve it. (disgusting, I know, I'll find a better solution on the second Tuesday of next week, maybe... hopefully... we'll see.)

The problem is, Overseerr doesn’t seem to realize they’re offline. So when someone makes a request during that downtime, Overseerr still tries to dispatch it to the 'arrs and it silently fails. The media ends up stuck in a Requested state, but there’s no actual request behind it.

---

For example ( image^[1] | image^[2] ), here's a movie that is stuck in the Requested state, but when I hit the API (/api/v1/request/{id}), there’s no request tied to it. It doesn’t show up under Requests page either.

I understand the irony in me asking this, because my own stack needs better health checks, but I request that Overseerr have a better way in checking if the services are receiving the request. Maybe...

• Perform a dependency health check before dispatching to the services (Radarr/Sonarr).
• If a service is down, show a "Retry" button or fail cleanly, which looks to already be implemented.
• Avoid setting the "Requested" flag unless confirmation is received from Radarr/Sonarr.

But it gets worse...

The real problem is that there’s no way to find all of the media items with broken request states. They don’t appear in the Requests view, and there’s no history on the media itself. I only found this one because I went to request it myself, but I'm guessing someone requested it a while back, but it didn't go through.

How many pieces of media are in this broken state? Is there a quick API query I can pass through to find media items that are in the requested state, but don't have a valid request? I'm not familiar with the database structure or the way the Requested stated is given to help myself... but from what I do understand is that when you request an item, it gets added the the media table and that gives it the requested status (since the status given on commit is 2). I'm not sure, but if anyone would like to give me a hand, that would be great!

Actually... maybe not

Now that I've crawled through the database, I've noticed a pattern with the database entries and media items that have the above issue. In the database, I looked for items that had a blank mediaAddedAt column, with the status of 2 (pending). There were only a few.^[3] They have been deleted.

---

Well, shit. As I'm writing this, I guess I've some how figured out how to fix my main concern lol, but I think I'm going to leave this up so others can join the discussion, maybe give me some feedback on what I should do to fix the primary issue. I don't think this warrants a Github issue just yet, unless many others are having the same issue.

Probably not, because they don't have a janky vpn/container setup.

Anyways, before I push this as a bug, I'd like others to chime in to see if this is just a me issue or not.

Thanks!

---

If you don't like imgur, I've uploaded the images to GitHub as well:
^[1] github-4071fe02-aae6-47c8-b86f-d8638741c18a
^[2] github-ca47660c-9326-4290-b987-0e364ffd785d
^[3] github-748d1c11-8a4f-4cf9-a1c8-2c928c56e2a6