read_discover 'requested' browse category returns empty despite existing requests #3
Notifications
Due Date
No due date set.
Depends on
Reference: gronod/ombi-mcp#3
Reference in New Issue
Block a user
Summary
read_discoverbrowsewithcategory: "requested"returns an empty page for both movie and tv, even though requests exist on the instance (e.g. movieYummyrequest 2207, tvSeven Up!— both approved and visible viaread_requests recent).Environment
develop@d047d76Reproduction
Both return
{"items":[], "total":0}.Expected
Requested-media listings contain at least the recently requested items.
Actual
Empty result pages for both media types.
Notes
Handler routes to
GET /api/v2/Search/{media}/requested/{pos}/{amt}. Unclear whether the upstream route returns an empty array legitimately or the route/argument order is wrong — needs wire-level verification. Filed as suspected defect pending classification.Correlation IDs
Observed during the live read-tool sweep; representative
29465510b7e7503f8371e718(browse cluster)