#Large Page Data when adding Friends (1994) TV series

49 messages · Page 1 of 1 (latest)

karmic stump
#

I can't create a request for the TV series Friends, In the UI I get the error

Something went wrong while submitting the request.
And in the container logs I see
Warning: data for page "/tv/[tvId]" (path "/tv/1668") is 356 kB which exceeds the threshold of 256 kB, this amount of data can reduce performance.
See more info here: https://nextjs.org/docs/messages/large-page-data
This has been an issue since I first setup Seerr and migrated from Ombi but I've not had any issues adding any other TV series or movie via API or WebUI.

I'm not sure if this is related to https://github.com/sct/overseerr/issues/3076

GitHub

Description Using the official docker image there's a couple items in the logs that (hopefully) look like they can be low hanging fruit to solve. Warning: data for page "/" is 179 kB ...

dreamy spade
#

The warning has nothing to do with it

#

Thats not relevant at all

#

I need your logs

#

Full logs

#

And no that issue is also not relevant

#

That warning doesnt do anything. Its just a little warning by nextjs because we have page data set to 256kb by default and it does nothing

#

Your issue is something else

#

We need your full logs.

karmic stump
dreamy spade
#

I would recommend trying to request right now

#

And then send the log when it errors out

#

Otherwise itd be very hard for us to go through the logs

karmic stump
# dreamy spade I would recommend trying to request right now

Cool, I only provided the whole days log because you said "Full logs" and I didn't want to waste your time by drip feeding you.

I tail'ed the log file and then

  1. opened a browser tab to Overseerr
  2. Entered Friends in the search
  3. Selected the show in the search results to open the page with the shows details
  4. Clicked the Request button at 07:40:50Z
  5. Received the usual error in the WebUI

But nothing much in the log file. I won't bother creating a gist as its just...

2026-02-10T07:40:26.516Z [error][Plex.TV Metadata API]: Failed to retrieve watchlist items {"errorMessage":"Request failed with status code 404"}
2026-02-10T07:43:35.844Z [error][Plex.TV Metadata API]: Failed to retrieve watchlist items {"errorMessage":"Request failed with status code 404"}
2026-02-10T07:43:38.475Z [error][Plex.TV Metadata API]: Failed to retrieve watchlist items {"errorMessage":"Request failed with status code 404"}
dreamy spade
dreamy spade
# karmic stump

okay so the request isnt reaching your server and failing in frontend

#

so what you should do is

#

right click on browser

#

press inspect

#

then go to network tab

#

and have that open while you try to request

#

you should see a request in network logs that is 500 status code (in pink/purplish color)

#

select that

#

check the response

#

and send me the response

karmic stump
# dreamy spade and send me the response

Request header

POST /api/v1/request HTTP/1.1
Accept: application/json, text/plain, */*
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.9
Connection: keep-alive
Content-Length: 195
Content-Type: application/json
Cookie: connect.sid=s%3A-frDBTSI61_VGa1g1ujKzdDCmrgmdjTC.bMRStC0ReaQK6DLMy9GDauvnED0RT03PbCdohfaLokQ
Host: 10.1.3.234
Origin: http://10.1.3.234
Referer: http://10.1.3.234/tv/1668
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36

Payload

{"mediaId":1668,"tvdbId":79168,"mediaType":"tv","is4k":false,"seasons":[0,1,2,3,4,5,6,7,8,9,10],"serverId":0,"profileId":7,"rootFolder":"/downloads","languageProfileId":1,"userId":1,"tags":[4,9]}

Response

{"message":"SQLITE_CONSTRAINT: UNIQUE constraint failed: media.tvdbId"}

Response header

HTTP/1.1 500 Internal Server Error
X-Powered-By: Express
Content-Type: application/json; charset=utf-8
Content-Length: 71
ETag: W/"47-Bd1QcBFqeIJLFayLG35Hu9FVcdQ"
Date: Wed, 11 Feb 2026 10:40:46 GMT
Connection: keep-alive
Keep-Alive: timeout=5
dreamy spade
#

Are you fine with editting db?

#

We can get it fixed then

karmic stump
#

From the sqlite error I take it the tvdbid already exists in the database so it cant append a new record because the ID wouldn't be unique?

dreamy spade
#

Which got cached in your db

#

Persisted

#

Its a metadata provider fuck up

#

Stop seerr

#

Go to config folder

#

Open your db via sqlite3

#

Run this

#
SELECT * FROM media WHERE tvdbId = 79168;
#

Send output

karmic stump
# dreamy spade Send output
sqlite> SELECT * FROM media WHERE tvdbId = 79168;
8581|tv|79168|79168||3|2025-03-16 02:01:14|2025-10-04 15:32:09|2025-03-16 02:01:14|3||0|2|535|535|friends|friends||
dreamy spade
#

I see. It was probably a failed media request thats stale

#
DELETE FROM media_request WHERE mediaId IN (SELECT id FROM media WHERE tvdbId = 79168);
DELETE FROM season WHERE mediaId IN (SELECT id FROM media WHERE tvdbId = 79168);
DELETE FROM season_request WHERE requestId IN (SELECT id FROM media_request WHERE mediaId IN (SELECT id FROM media WHERE tvdbId = 79168));
DELETE FROM media WHERE tvdbId = 79168;
#

You can run these to clear

karmic stump
#

Cool thats removed that record. Will start it up again and try a request?

karmic stump
#

Thank you @dreamy spade