The Basics
- Nextcloud Server version (e.g., 29.x.x):
34.0.2
- Operating system and version (e.g., Ubuntu 24.04):
docker image: nextcloud:34-fpm
- Web server and version (e.g, Apache 2.4.25):
docker image: nginx:stable
- Reverse proxy and version _(e.g. nginx 1.27.2)
docker image: jc21/nginx-proxy-manager:2
- PHP version (e.g, 8.3):
included in docker image
- Is this the first time you’ve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
a few days ago
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
docker
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
no
Summary of the issue you are facing:
Since a few days the admin page of the “memories” app tells me:
“Looks like it has been more than an hour since the last index job was run. Make sure Nextcloud cron is configured correctly.”
A few days ago I noticed a stale background job related to the memories app which was running for several days.
# ./occ_exec.sh background-job:running
+--------------------+----------------------------+---------------------+-----------+-----+---------------+
| Run ID | Class | Started at | Server ID | PID | Running since |
+--------------------+----------------------------+---------------------+-----------+-----+---------------+
| 107722951783895040 | OCA\Memories\Cron\IndexJob | 2026-07-18 07:00:04 | 482 | 117 | > 13 days |
+--------------------+----------------------------+---------------------+-----------+-----+---------------+
I tried to kill that job. With the help of some AI tools I finally found the commands to remove that job:
DELETE FROM oc_job_runs WHERE run_id = 107722951783895040;
DELETE FROM oc_job_runs WHERE status = 0;
A day later or so when I checked the memories admin page I saw that message:
“Looks like it has been more than an hour since the last index job was run. Make sure Nextcloud cron is configured correctly.”
I know that the cronjob is running as always. If I manually execute the cronjob it finishes within a second and gives no error.
I tried to fix it with occ memories commands
occ memories:index --force
occ maintenance:repair
There have been no errors, but the message did not go away.
I waited 24 hours to see if some hidden daily task might solve the problem, but it didnt.
Any idea what is going wrong?
Thanks for your help.