Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. 
The Basics
- Nextcloud Server version (e.g., 29.x.x):
- 30.0.5.1
- Operating system and version (e.g., Ubuntu 24.04):
- ubuntu-server 24.04.1
- Web server and version (e.g, Apache 2.4.25):
- NGinx 1.27.0
- Reverse proxy and version _(e.g. nginx 1.27.2)
- NGinx 1.26.2
- PHP version (e.g, 8.3):
- 8.3
- Is this the first time you’ve seen this error? (Yes / No):
- Yes
- When did this problem seem to first start?
- after Upgrade from NC 30.0.4 to 30.0.5.1
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- Bare Metal
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
- No
Summary of the issue you are facing:
[…]
Steps to replicate it (hint: details matter!):
- I upgraded NC to 30.0.5.1 via command line
- I made integrity:check-core as usual
- I run the first cron jobs via occ and received the message (see title)
- The path is definitely empty because the user is not only very often with the shared folder.
- I shared a uploads folder “Uploads” with him - he has made his own folder twice called with same name so NC renamed is as “Uploads (2)”
My Problem now is - i can’t reach the path to delete something. I ended the share by deleting the share in WebUI but the folder created by user which is now called as “Uploads (2)” is still part of the memories index.
–force indexing again didn’t help after a files:scan --all and a files:scan-app-data as well
So i decided to stop flooding my logfile with the failure messages (see title) by using a RegEx exception as mentioned in the memories app → admin section
I appended the existing default exception by this
\/@(Recycle|eaDir|Uploads|Uploads.*)\/
The Problem “Uploads (2)” contains a space so i thought the .* option is a helping thing - but did not.
Log entries
Nextcloud
Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.
Failed to index folder /username/files/Freigaben/Uploads (2): File by id 9861853 not found
Web Browser
Web server / Reverse Proxy
The output of your Apache/nginx/system log in /var/log/____:
no other hints from reverse proxy
Does anyone have a tip which (correct) RegEx Expression should i use to avoid memories app indexing the path …/files/Freigaben/Uploads (2) ?
Is there any other way of solution (steps to reproduce) to get rid of the failure logs?
Update (changed RegEx but the result is the same failure …)
As i can see, regex101 gave me a match for Uploads (2) but the logfile gives still the error output so memories must have been indexing the path …
i am running out of ideas …
