# Memories app complaining about cron job

**URL:** <https://help.nextcloud.com/t/memories-app-complaining-about-cron-job/247617>\
**Category:** ℹ️ Support\
**Tags:** nc34, setup\_warning, memories-app\
**Created:** [August 3, 2026, 5:39am UTC](https://help.nextcloud.com/t/memories-app-complaining-about-cron-job/247617 "2026-08-03T05:39:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mabod](https://help.nextcloud.com/user_avatar/help.nextcloud.com/mabod/32/7867_2.png) [@mabod](https://help.nextcloud.com/u/mabod)\
**Post date:** [August 3, 2026, 5:39am UTC](https://help.nextcloud.com/t/memories-app-complaining-about-cron-job/247617/1 "2026-08-03T05:39:13Z")

</div>

## 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.

```auto
# ./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:

```auto
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.

---

<div class="post-metadata">

**Author:** ![mabod](https://help.nextcloud.com/user_avatar/help.nextcloud.com/mabod/32/7867_2.png) [@mabod](https://help.nextcloud.com/u/mabod)\
**Post date:** [August 3, 2026, 3:12pm UTC](https://help.nextcloud.com/t/memories-app-complaining-about-cron-job/247617/2 "2026-08-03T15:12:43Z")

</div>

It is working again. The only thing I changed in the meantime was to disable the memories app and to enable it again a minute later. May be that fixed it. I dont know.

---

<div class="post-metadata">

**Author:** ![csplkr](https://help.nextcloud.com/letter_avatar/csplkr/32/5_5575768a8748004e209b776fc1b2916d.png) [@csplkr](https://help.nextcloud.com/u/csplkr)\
**Post date:** [August 16, 2026, 9:54pm UTC](https://help.nextcloud.com/t/memories-app-complaining-about-cron-job/247617/3 "2026-08-16T21:54:13Z")

</div>

Thanks, I had the same issue, but disabling and enabling the app and waiting a couple of minutes for the cron job to run fixed it for me, too.