File not found by id during indexing

[dwaxweiler]

Describe the bug

During the automatic and manual indexing, one file is not found, which I can see in the logs and on the console when running the command manually:

Failed to index folder /user1/files/filename: File by id 1714707 not found

Steps To Reproduce

Waiting for automatic or manual indexing results. It also happens with limiting the scan to the user in question:

php occ memories:index --user user1

Running php occ files:scan user1 did not help.

Platform

- OS: Debian GNU/Linux 11 (bullseye)
- Memories Version: 7.4.1
- Nextcloud Version: 29.0.9
- PHP Version: 8.2.26

Screenshots

No response

Additional context

No response

[MrRinkana]

If you browse the data folder yourself, can you find the file?

What are the permissions of the file (ls -la)?

[dwaxweiler]

If you browse the data folder yourself, can you find the file?

No, this file does not exist.

[MrRinkana]

Then this issue is about stale index entries not being removed.

Do you know how the file got removed? Was/is it added to an album? Info about its lifetime can help the debugging.

External storage (app) or nextcloud internal?

Your issue should be resolved if you run occ memories:index --user user1 --force

But if it does not bother you too much, you could let it be for a while to try to hunt down a cause or steps to reproduce.

[dwaxweiler]

Do you know how the file got removed? Was/is it added to an album? Info about its lifetime can help the debugging.

No, unfortunately, I don't know. We don't use the album feature; The Photos app is deactivated.

Suspicious is that this file has no file extension in the log file, but it as a dot a bit earlier in the name: /user1/files/Recrutement chargé.e de mission juin 2024 Could this have caused an issue somewhere?

External storage (app) or nextcloud internal?

This file path points to the internal folder of a user, and we are also using group folders. I could imagine that this file was moved from the personal to a group folder.

Your issue should be resolved if you run occ memories:index --user user1 --force

Unfortunately, it does not. It ends with the same error message.