I
Immich•3w ago
AKTK

Ambiguous column error when rerunning duplicate detection on v1.133.0

Just upgraded to v.1.133.0 and all seems fine, other than when I click "MISSING" on the Duplicate Detection I see the below error in the logs: 
[Nest] 17  - 05/21/2025, 8:44:44 PM   DEBUG [Api:LoggingInterceptor~4vm1ywwl] PUT /api/jobs/duplicateDetection 200 3.13ms 51.148.136.198
Query failed : {
  durationMs: 1.138799000007566,
  error: PostgresError: column reference "assetId" is ambiguous
      at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)
      at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)
      at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)
      at Socket.emit (node:events:518:28)
      at addChunk (node:internal/streams/readable:561:12)
      at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
      at Readable.push (node:internal/streams/readable:392:5)
      at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {
    severity_local: 'ERROR',
    severity: 'ERROR',
    code: '42702',
    position: '155',
    file: 'parse_relation.c',
    line: '887',
    routine: 'colNameToVar'
  },
  sql: 'select "assets"."id" from "assets" inner join "smart_search" on "assets"."id" = "smart_search"."assetId" inner join "asset_job_status" as "job_status" on "assetId" = "assets"."id" where "assets"."visibility" != $1 and "assets"."deletedAt" is null and "job_status"."duplicatesDetectedAt" is null',
  params: [ 'hidden' ]
}
[Nest] 7  - 05/21/2025, 8:44:44 PM   ERROR [Microservices:{"force":false}] Unable to run job handler (queue-duplicate-detection): PostgresError: column reference "assetId" is ambiguous
PostgresError: column reference "assetId" is ambiguous
    at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)
    at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)
    at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
[Nest] 17  - 05/21/2025, 8:44:44 PM   DEBUG [Api:LoggingInterceptor~4vm1ywwl] PUT /api/jobs/duplicateDetection 200 3.13ms 51.148.136.198
Query failed : {
  durationMs: 1.138799000007566,
  error: PostgresError: column reference "assetId" is ambiguous
      at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)
      at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)
      at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)
      at Socket.emit (node:events:518:28)
      at addChunk (node:internal/streams/readable:561:12)
      at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
      at Readable.push (node:internal/streams/readable:392:5)
      at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {
    severity_local: 'ERROR',
    severity: 'ERROR',
    code: '42702',
    position: '155',
    file: 'parse_relation.c',
    line: '887',
    routine: 'colNameToVar'
  },
  sql: 'select "assets"."id" from "assets" inner join "smart_search" on "assets"."id" = "smart_search"."assetId" inner join "asset_job_status" as "job_status" on "assetId" = "assets"."id" where "assets"."visibility" != $1 and "assets"."deletedAt" is null and "job_status"."duplicatesDetectedAt" is null',
  params: [ 'hidden' ]
}
[Nest] 7  - 05/21/2025, 8:44:44 PM   ERROR [Microservices:{"force":false}] Unable to run job handler (queue-duplicate-detection): PostgresError: column reference "assetId" is ambiguous
PostgresError: column reference "assetId" is ambiguous
    at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)
    at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)
    at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
Is this a known thing or something that others are seeing too?
7 Replies
Immich
Immich•3w ago
:wave: Hey @AKTK, Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA Checklist I have... 1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: read applicable release notes. 3. :ballot_box_with_check: reviewed the FAQs for known issues. 4. :ballot_box_with_check: reviewed Github for known issues. 5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy). 6. :blue_square: uploaded the relevant information (see below). 7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable (an item can be marked as "complete" by reacting with the appropriate number) Information In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider: - Your docker-compose.yml and .env files. - Logs from all the containers and their status (see above). - All the troubleshooting steps you've tried so far. - Any recent changes you've made to Immich or your system. - Details about your system (both software/OS and hardware). - Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h). - The version of the Immich server, mobile app, and other relevant pieces. - Any other information that you think might be relevant. Please paste files and logs with proper code formatting, and especially avoid blurry screenshots. Without the right information we can't work out what the problem is. Help us help you ;) If this ticket can be closed you can use the /close command, and re-open it later if needed.
AKTK
AKTKOP•3w ago
Interestingly a full "All" doesn't show the error, but the "Missing" does
Zeus
Zeus•3w ago
Hello, please open a GitHub Issue to track Likely we will need to patch this #18433
Immich
Immich•3w ago
[Pull Request] fix(server): missing button for duplicate detection not working (immich-app/immich#18433)
AKTK
AKTKOP•3w ago
Damn y'all are quick, still want mew to open an issue for tracking or happy for the PR to capture it all?
Daniel
Daniel•3w ago
It's fine now, thanks! I think it's just that nobody expected mertalev to fix it this quickly 😅
Immich
Immich•3w ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?