Requests
The intake queue: what the household has asked for, from every route they can ask by.
Work the queue
- Read the row: what was asked for, who asked, and when.
- Press Approve to add it to Sonarr or Radarr, or Decline to close it.
- Approving is the only action that downloads anything. Tagging does not approve, and neither does anything else on this screen.
Approve and Decline on a Seerr request act in Overseerr itself, not only here. If an Arr rule is set to trigger on request, Kustos approves matching pending requests on its own within about two minutes, so some requests will be approved before you see them.
Where a request can come from
| Source | How it arrives | Delay |
|---|---|---|
| A watchlist | Somebody adds a title to their Plex or Trakt watchlist. | Polled every 15 minutes, so minutes rather than a day. |
| Seerr | Overseerr or Jellyseerr. | As fast as Kustos can read the feed. |
When requests stop appearing
Seerr requests only arrive while Kustos can read the Seerr feed. If Overseerr is down, every rule that triggers on a request is skipped, and Kustos records that as a problem on the affected rule rather than only failing a task. So a request rule that "never fires" is usually a connection problem. Check the Overseerr card on Connections first.
Per-user import tags. With the import-tag switch on, the requester's own tag (set on their People card) goes on the title. Requests Kustos approves or adds itself carry it from the start. A request approved inside Overseerr reaches Sonarr/Radarr untagged and gets the tag on the next import-tag sync, within six hours; until then, per-user rules and collections can't see it. Without the switch the title arrives untagged, so per-user rules and collections can't see it and nothing records who wanted it. Tags are matched against the ones your arr already has — never invented — so a requester with no tag on that arr is skipped and logged. Tagging doesn't approve anything.