#Override Rules Greyed Out - Just Me? v. 3.2.0
75 messages · Page 1 of 1 (latest)
Override rules is live since v2. And has been used by everyone. Sounds like there might be an issue with the state/db. Not sure
Could you do this
Delete the radarr service
And re-add
Lets see if that fix. If not we will have to debug
Thank you for the suggestion, I've added a new instance of the Sonarr service with no change, I can create a brand new Sonarr/Radarr container and see if that works.
That wont
Its related to seerr
Are you comfortable with running sqlite queries?
So we can take a look at the db to see why this is happening
Sorry was off trying that, you're, right no change
Actually can you share your network logs
When you open modal and select a service in the service filed
So we can see what is being returned
From the endpoint
That should help us figure out the issue
Will have to debug through you because i cant recreate
For context
Nope. Need the full network logs. You could export it as a har file and share
I'm accessing Seerr via a CF Tunnel that may change things?
Don't think so but try accessing locally first. And then share har file of locally so you wont have to clean up har file
look for something with "/api/v1/settings/xxx/test"
something must be failing around that call
because before that everything is disabled (except the service dropdown)
once this successes, the fields become available
could you open the console
reload the page
and then do this again please?
i think the info from when the page loaded are missing
It's now working
Locally anyway let me try CF tun
So sorry to have wasted everyone's time it looks like a browser thing
It looks like Sonarr works but Radarr doesn't it most likely a me thing, I'll check it out
Hey all, just wanted to update a few of the things I've tried:
Seerr v3.2.0 (ghcr.io/seerr-team/seerr:latest, up to date)
Radarr + Sonarr in Docker on a shared bridge network
Accessed via local IP (192.168.0.248:5055) and Cloudflare Tunnel
Both Radarr and Sonarr using container hostnames (radarr:7878, sonarr:8989)
Symptom
Override Rules modal — Service dropdown works, all subsequent dropdowns (Root Folder, Quality Profile, Language Profile) are empty and non-interactive for both Radarr and Sonarr.
What we ruled out via HAR analysis
❌ API/network issue — POST /api/v1/settings/radarr/test fires and returns 200 OK with full profile and root folder data
❌ Adblocker/extension — reproduced in Brave (shields down, no extensions) and Chrome incognito
❌ Browser cache — cleared site data, tested multiple browsers
❌ Cloudflare Tunnel — reproduced on local IP only
❌ Authentication — Plex login and local Seerr account both affected
❌ API key/connectivity — wget from inside Seerr container to radarr:7878/api/v3/rootfolder returns correct data
❌ Stale settings — deleted and re-added both services, no change
Key observation
The Settings edit pencil for both Radarr and Sonarr correctly populates all dropdowns. The bug is isolated entirely to the Override Rules modal. The data is being fetched successfully but is not rendering in the component.
Additional note
Sonarr worked briefly on one occasion (dropdowns populated, was able to interact) then stopped working again the next day with no config changes made.
Suspected cause
Possible regression in the Override Rules modal component in v3.2.0, potentially related to the fix that was previously merged as (overriderules) Test service using the right endpoint (#2399).
Doubt thats the problem
I am on 3.2.0 and I can select all dropdowns
Including root folders
#2399 was not included in v3.2.0, so that's not the cause here.
Hey @slow pilot. Just to check, was the suspected cause section written with the help of an AI tool? #2399 wasn't included in v3.2.0, so that part isn't accurate. If you are using AI for debugging, I'd recommend avoiding it to ask for suggestions for issues like this as it tends to hallucinate plausible-sounding but incorrect causes which doesn't bring much value and only adds noise to the discussion. Several users are running Override Rules fine on 3.2.0 (see #general message), so it's not a version regression. Your actual troubleshooting steps were solid though, that's helpful info!
I actually might have narrowed down the issue
Im pushing a possible fix
would you mind testing that preview image for me?
please use preview-debug-overriderules tag when
https://github.com/seerr-team/seerr/actions/runs/24603334648
finishes (in about 8 mins)
It was just asked for the round up on what I tried
I'll give this a go, thank you!
We have lift off 🛫 thank you for your suggestions and assistance on it
Lets gooo
@gleaming urchin
You did this. You broke this
You tried to match an array slice index with an object id 🗿
I saw a post on the git that someone else broke it too, shall I point them in the direction of the build you sent?
Yes
what, how 🗿
what's wrong 🗿
radarrServices is a plain array
radarr.id is an id that can be any number. It is not the array index
so for example if your only radarr service has an id of 3 it will live in radarrSerices[0] but your code is looking for radarrServices[3] 🗿
You're matching an ID to an array index, which is incorrect 🗿
Most of the users do not face this issue as it works by accident. For example, my radarr/sonarr service ID happen to match their array indices because it is my very first service and it never got deleted so its id is 0 which sits at radarrService[0] and the buggy index lookup accidentally worked because id and the index are the same number
guess who wrote this 
Oh yeah yeah 🗿