starred/immich

Fork 0

mirror of https://github.com/immich-app/immich.git synced 2026-03-02 22:57:45 -05:00

Unassigned faces start showing up later #3108

New issue

Closed

opened 2026-02-20 02:04:26 -05:00 by deekerman · 0 comments

deekerman commented

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

Owner

Originally created by @diyoyo on GitHub (Jun 13, 2024).

The bug

First, I'm sorry because I don't really understand what "Unassigned faces" is all about. I couldn't find anything in the documentation, but I just realized it is related to the following problem:

Face Detection and Face Clustering is performed
I start tagging faces, merging people, hiding others, etc.
There are some pics where not everyone is available for tagging: either because it is labelled as "Unassigned face" or just because it was not detected (i guess)
When I'm done with tagging, I run Face Detection and Face Clustering again
Then new people appear that are available for tagging: either from the unassigned faces or from the pool that was missed before.

I feel like this is a bug: I can never predict the amount of work it's going to take me to tag everyone, since it keeps adding up.
Why is a face unassigned in the first place? Why are some faces detected afterwards that were not detected the first time?
Are there some threshold that I meet only after I reduced the number of unknown people?

I played a little bit with the settings to understand things better, but even using min-cluster-size of 1 and asking immich to display all available people in the people tab (by editing repositories/person.repository.js ), I still have some new people showing up after I have spent time tagging people.
I also tried with a smaller library (18GB instead of 500GB), but the behavior is the same, to a smaller extent, or course, but still.

Thanks for the help as I am very confused.

The OS that Immich Server is running on

Debian 12

Version of Immich Server

v1.106.3

Version of Immich Mobile App

v1.106.3

Platform with the issue

Server
Web
Mobile

Your docker-compose.yml content

Not relevant

Your .env content

Not relevant. no modification of the settings

Reproduction steps

- Face Detection and Face Clustering is performed
- I start tagging faces, merging people, hiding others, etc.
- There are some pics where not everyone is available for tagging: either because it is labelled as "Unassigned face" or just because it was not detected (i guess)
- When I'm done with tagging, I run Face Detection and Face Clustering again
- Then new people appear that are available for tagging: either from the unassigned faces or from the pool that was missed before.

Relevant log output

No response

Additional information

No response

Originally created by @diyoyo on GitHub (Jun 13, 2024). ### The bug First, I'm sorry because I don't really understand what "Unassigned faces" is all about. I couldn't find anything in the documentation, but I just realized it is related to the following problem: - Face Detection and Face Clustering is performed - I start tagging faces, merging people, hiding others, etc. - There are some pics where not everyone is available for tagging: either because it is labelled as "Unassigned face" or just because it was not detected (i guess) - When I'm done with tagging, I run Face Detection and Face Clustering again - Then new people appear that are available for tagging: either from the unassigned faces or from the pool that was missed before. I feel like this is a bug: I can never predict the amount of work it's going to take me to tag everyone, since it keeps adding up. Why is a face unassigned in the first place? Why are some faces detected afterwards that were not detected the first time? Are there some threshold that I meet only after I reduced the number of unknown people? I played a little bit with the settings to understand things better, but even using min-cluster-size of 1 and asking immich to display all available people in the people tab (by editing `repositories/person.repository.js` ), I still have some new people showing up after I have spent time tagging people. I also tried with a smaller library (18GB instead of 500GB), but the behavior is the same, to a smaller extent, or course, but still. Thanks for the help as I am very confused. ### The OS that Immich Server is running on Debian 12 ### Version of Immich Server v1.106.3 ### Version of Immich Mobile App v1.106.3 ### Platform with the issue - [X] Server - [X] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML Not relevant ``` ### Your .env content ```Shell Not relevant. no modification of the settings ``` ### Reproduction steps ```bash - Face Detection and Face Clustering is performed - I start tagging faces, merging people, hiding others, etc. - There are some pics where not everyone is available for tagging: either because it is labelled as "Unassigned face" or just because it was not detected (i guess) - When I'm done with tagging, I run Face Detection and Face Clustering again - Then new people appear that are available for tagging: either from the unassigned faces or from the pool that was missed before. ``` ### Relevant log output _No response_ ### Additional information _No response_

deekerman closed this issue

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

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/immich#3108

No description provided.

Rows
Columns