Memories not working

[Liaders]

Memories were working few weeks ago when I initially set up Immich.
I exexuted command:
/opt/immich-app# docker compose exec --user postgres database psql -Ppager=no -d immich -c 'select "createdAt", type, "memoryAt", "showAt", "hideAt", "seenAt" from memory order by 1' createdAt | type | memoryAt | showAt | hideAt | seenAt -----------+------+----------+--------+--------+-------- (0 rows)
result:
createdAt | type | memoryAt | showAt | hideAt | seenAt -----------+------+----------+--------+--------+-------- (0 rows)
double checked with server.com/api/memories
result:
[]

What I tried from other closed issues:

1. Deleting and starting Memories from webui
   2.docker compose exec --user postgres database psql -d immich -c 'TRUNCATE TABLE memory RESTART IDENTITY CASCADE;'
   3. docker exec immich_postgres psql --dbname=immich --username=postgres -c "delete from system_metadata where key like 'memory-state'; truncate table memory cascade;"
   4. curl -X PUT "https://<immich-host>/api/jobs/backgroundTask" \ -H "X-Api-Key: <ADMIN_API_KEY>" -H "Content-Type: application/json" \ -d '{"command":"resume","force":true}'
   Nothing from above fixed the issue
   There is nothing related to memories in Immich logs

[skatsubo]

Hey!
Thank you for providing detailed info. It seems you already performed pretty solid troubleshooting 👍

---

For context, memories involve the following logical blocks/steps.

1. Create and execute a background job.
   Jobs/queue management is done with BullMQ and needs healthy Redis.
   You either trigger the memory generation job through "Administration > Jobs > Create job" or wait for the scheduled nightly job execution at 00:00 local time, iirc. Docs: https://docs.immich.app/administration/jobs-workers/#jobs.
   Then a worker picks up this new job and runs step 2.

2. Generate memory records for existing assets "on this day".
   Immich generates memories in bulk for dates { -3, -2, -1, 0, +1, +2, +3 } relative to the current day.
   Obviously, there should be assets for "this day" N years ago, otherwise nothing will be added to memory / memory_asset tables.
   If the memory generation ran at least once, then it sets memories-state in the system_metadata table.
   Generated memories are available through API at https://my.immich.app/api/memories (nothing in your case).

3. Fetch memories on client/frontend.
   A client/frontend calls API like: https://my.immich.app/api/memories?for=2025-10-29T12%3A00%3A00.000Z

---

I suggest the following troubleshooting steps.

1. Go to the Jobs page.

2. Are there paused jobs? It will be reported in the top right corner if anything is paused. You can also check https://my.immich.app/api/jobs.
   (You already did "resume backgroundTask" though API. So this is just to double-check)

3. Trigger the memories generation job. (If you have Verbose logging level enabled, it will print something in logs)

4. Check system_metadata

select from system_metadata where key like 'memories-state';

5. If there is nothing, then most likely the job was not picked up by a worker. Typically jobs go through these phases/events added -> waiting -> active -> completed -> drained.

6. Check queue/job events in Redis. To fetch last 100 events for the backgroundTask queue:

docker exec immich_redis redis-cli --raw XREVRANGE "immich_bull:backgroundTask:events" + - COUNT 100 | \
  awk '/^[0-9]+-[0-9]+$/ { if (NR > 1) print output ; output = "ID=" $0 ; next }
  { if (!key) { key = $0 } else { output = output ", " key "=" $0 ; key = "" } }
  END { print output }'

(The command is quite long because it transforms Redis output into something readable.)

7. Is the memory job there in backgroundTask events?

---

If you want to go deeper with Redis, all queues/jobs can be dumped with even longer command - #20548 (reply in thread).
Also there is the bullboard UI, can be added to compose:

  bullboard:
    image: venatum/bull-board:latest
    environment:
      REDIS_HOST: redis
      BULL_PREFIX: immich_bull
    ports:
      - "3000:3000"

---

There is nothing related to memories in Immich logs

Right, these background jobs are not chatty. Probably adding a log message here and there won't hurt.