Issue Reporting and Re grab

Issue Reporting and Re-grab

Reporting an issue

Users run /issue <title> to report a problem (Video / Audio / Subtitle / Other) with media already on the server. The bot searches movies and TV, limits results to in-library titles, applies the same link gate as requests (Account Linking), then collects a short description and files it to Seerr's issue tracker.

For TV, the form also asks which season and episode is affected, so issues are pinned to a single episode.

Attribution

• On Seerr 3.4+ the issue is filed under the reporter's own Seerr account (linked users).
• On older servers — where the API attributes every API-key issue to the admin account — the real reporter is recorded in the issue message instead.

Either way the reporter is tracked locally, so the dashboard and resolution DMs know who filed it.

Handler notifications

When an issue is filed, VaultRequestrr DMs the configured issue handlers (and posts to an optional issue channel) with a card carrying Re-grab and Resolve buttons — persistent, like the request buttons.

Who gets issue notifications (and can act on them) and which channel they post to are set on the dashboard Settings → Approvals & Issues → Issue notifications card — leave either field blank to reuse the request approvers / approvals channel.

Re-grab: the fix for a bad file

Re-grab is the one-button fix for a bad/corrupt file. It:

1. Sets the title monitored (Radarr/Sonarr won't grab for an unmonitored item).
2. Runs an interactive search and grabs a replacement — the existing file is only deleted once a release is found.
3. Excludes and blocklists the release that produced the bad file, so the identical release can't come back. Season packs are skipped when fixing a single episode.
4. Keeps the issue open until the replacement actually finishes downloading and imports — VaultRequestrr watches the arr queue, resolves the issue (and DMs the reporter) on import, and reopens the card with a warning if the download dies.

Outcomes are synced to every copy of the card (each handler's DM and the channel post), so a second admin can't accidentally fire a duplicate re-grab.

Resolve simply marks the issue resolved.

Dashboard actions

The same actions live on the Admin Dashboard Issues page, plus a few that need the direct Radarr/Sonarr connections:

• Details — the current file's quality/size/languages, monitored state, and live download-queue progress, read straight from the arr.
• Re-search — deletes the current file and triggers a fresh search (movie file for movies; just the reported episode's file for TV). Radarr/Sonarr can't "blocklist but keep the file" for an already-imported release, so removing the file is what reliably forces a new grab.
• Manual search — run an interactive indexer search and grab a specific release from the candidate list, instead of relying on auto-search.
• Resolve / reopen, and remove/clear for resolved issues.