Handle duplicate movie name #9280

New issue

Closed

opened 2026-02-20 00:12:26 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 00:12:26 -05:00

Owner

Originally created by @julienbenjamin on GitHub (Oct 12, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

Sometimes, movies with the same name are released the same year.

If you leave the original proposed name, you cannot add more than the first one, unless you specify another name for storage.

The actual issue is there is no message displayed to the user.

Expected Behavior

I would at least expected to have an error message displayed.

As to how to handle actual duplicates, I have no idea for the same language (if the original title can be used, maybe that's a way to handle part of it) - especially since I would prefer actual duplicate versions of a movie being handled by Radarr, but that's a separate discussion. It's worth mentioning if the potential handling covers both cases.

Steps To Reproduce

Add "I Swear (2025) -> https://www.themoviedb.org/movie/1317149-i-swear
Add "I Swear (2025) -> https://www.themoviedb.org/movie/1044736-je-le-jure
See how Radarr does not add the second one in the same location without error message.

Environment

- OS: TrueNAS Scale  25.04.2.3 (Debian 12)
- Radarr: 6.0.2.10271
- Docker Install: Yes
- Using Reverse Proxy: No
- Browser: Firefox 143
- Database: Sqlite 3.50.4

What branch are you running?

Master

Trace Logs? Not Optional

trace_log.txt

Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @julienbenjamin on GitHub (Oct 12, 2025). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Current Behavior Sometimes, movies with the same name are released the same year. If you leave the original proposed name, you cannot add more than the first one, unless you specify another name for storage. The actual issue is there is no message displayed to the user. ### Expected Behavior I would at least expected to have an error message displayed. As to how to handle actual duplicates, I have no idea for the same language (if the original title can be used, maybe that's a way to handle part of it) - especially since I would prefer actual duplicate versions of a movie being handled by Radarr, but that's a separate discussion. It's worth mentioning if the potential handling covers both cases. ### Steps To Reproduce 1. Add "I Swear (2025) -> https://www.themoviedb.org/movie/1317149-i-swear 2. Add "I Swear (2025) -> https://www.themoviedb.org/movie/1044736-je-le-jure 3. See how Radarr does not add the second one in the same location without error message. ### Environment ```markdown - OS: TrueNAS Scale 25.04.2.3 (Debian 12) - Radarr: 6.0.2.10271 - Docker Install: Yes - Using Reverse Proxy: No - Browser: Firefox 143 - Database: Sqlite 3.50.4 ``` ### What branch are you running? Master ### Trace Logs? **Not Optional** [trace_log.txt](https://github.com/user-attachments/files/22871847/trace_log.txt) ### Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [x] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 00:12:26 -05:00

closed this issue
added the
Type: Bug

Area: UI

Status: Maybe One Day

Status: Won't Fix
labels

deekerman commented

2026-02-20 00:12:26 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Oct 12, 2025):

The wiki calls out adding the tmdbid or imdbid to the folder name to resolve this.

Not a bug. But yes the UX for the rejection could be enhanced one day.

@bakerboy448 commented on GitHub (Oct 12, 2025): The wiki calls out adding the tmdbid or imdbid to the folder name to resolve this. Not a bug. But yes the UX for the rejection could be enhanced one day.