Subtitles choice desapears until manual metadata refresh on a specific movie/episode

[QuentinGG]

Describe The Bug
On a movie/episode page, subtitles selection option keep disapearing in the web interface. The dropdown menu that allows the subtitles choice is nowhere to be seen, even if the correct subtitle file(s) is present on the server. I have to refresh the metadata of the specific movie I want to watch, then reload the page, then I have access to the dropdown menu. If I try to upload a new subtitle file, it refreshed the metadata as well but now displays 2 subtitles options as there are now duplicate... This is very annoying. if I come back to the movie/episode page a few hours/days later, the dropdown is gone again. Obvisously when the dropdown menu doesn't appear, I can't access the subtitles during playback as well.

Steps To Reproduce

I can't seem to find anyone else on the web with the same issue.

1. Go to a movie/episode page with known external subtitles, notice that there is no subtitle dropdown menu
2. Click on '...' and then on "Refresh metadata"
3. Reload the movie/episode page
4. The subtitles dropdown menu now appears and subtitles are available during playback.

Expected Behavior
The dropdown menu shoud be there by default when a movie/episode have external subtitles files, and should also be available during playback.
I admit I have no idea if some default setting has changed during an update of Jellyfin but this behavior seems illogical.

Logs
I didn't see anything specific in the logs.

Screenshots
I don't think it's necessary

System (please complete the following information):

• Platform: Synology DSM, as a "native" app via the SynoCommunity repo, but it was the same using a Docker Container version.
• Synology NAS model: RS1221+ / AMD Ryzen V1500B / RAM 20Gb / 10Gb eth / NVMe caches
• Browser: Firefox, Safari and Chrome
• Jellyfin Version: 10.10.3 but I have been experiencing this since I updated from 10.8 to 10.9
• No hardware acceleration due to the AMD processor.
• No transcoding as it's too ressource intensive on the platform.

Thanks for considering this issue, or pointing out a setting I might have missed.