read_discover browse for tv categories popular and most_watched consistently fails with UPSTREAM_SCHEMA_MISMATCH: upstream response exceeded the read budget. Both categories worked on the earlier build (019caca) and returned items with tmdb identifiers — this is a regression on the post-M8 build (958006c).
{"error":{"code":"UPSTREAM_SCHEMA_MISMATCH","message":"upstream response exceeded the read budget"}}
anticipated and trending categories still work on the same build, as do all movie categories — so the failure is specific to the payload size of the popular/mostwatched TV routes, not auth or projection.
Expected
Either the read budget accommodates Ombi's real response sizes, or the handler pages/limits the upstream request so the result decodes.
Actual
The upstream body exceeds the client read budget and the call fails outright; consumers cannot browse the two most common TV discovery categories.
## Summary
`read_discover browse` for tv categories `popular` and `most_watched` consistently fails with `UPSTREAM_SCHEMA_MISMATCH: upstream response exceeded the read budget`. Both categories worked on the earlier build (`019caca`) and returned items with `tmdb` identifiers — this is a regression on the post-M8 build (`958006c`).
## Environment
- Binary: `/usr/local/bin/ombi-mcp`, `vcs.revision=958006cff264e058e2dc0637c01c091c93fef6d1`
- Ombi: 4.53.10, JWT auth
## Reproduction
```json
read_discover {"action":"browse","media":"tv","category":"popular","page":{"limit":3}}
read_discover {"action":"browse","media":"tv","category":"most_watched","page":{"limit":3}}
```
Both return:
```json
{"error":{"code":"UPSTREAM_SCHEMA_MISMATCH","message":"upstream response exceeded the read budget"}}
```
`anticipated` and `trending` categories still work on the same build, as do all movie categories — so the failure is specific to the payload size of the popular/mostwatched TV routes, not auth or projection.
## Expected
Either the read budget accommodates Ombi's real response sizes, or the handler pages/limits the upstream request so the result decodes.
## Actual
The upstream body exceeds the client read budget and the call fails outright; consumers cannot browse the two most common TV discovery categories.
## Correlation IDs
`ed43235f21533b068c0b73fa` (popular), `941fca47f5802fe498b86565` (most_watched), `145fd3630a8869f464834e9e` (popular, limit 25)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
read_discover browsefor tv categoriespopularandmost_watchedconsistently fails withUPSTREAM_SCHEMA_MISMATCH: upstream response exceeded the read budget. Both categories worked on the earlier build (019caca) and returned items withtmdbidentifiers — this is a regression on the post-M8 build (958006c).Environment
/usr/local/bin/ombi-mcp,vcs.revision=958006cff264e058e2dc0637c01c091c93fef6d1Reproduction
Both return:
anticipatedandtrendingcategories still work on the same build, as do all movie categories — so the failure is specific to the payload size of the popular/mostwatched TV routes, not auth or projection.Expected
Either the read budget accommodates Ombi's real response sizes, or the handler pages/limits the upstream request so the result decodes.
Actual
The upstream body exceeds the client read budget and the call fails outright; consumers cannot browse the two most common TV discovery categories.
Correlation IDs
ed43235f21533b068c0b73fa(popular),941fca47f5802fe498b86565(most_watched),145fd3630a8869f464834e9e(popular, limit 25)