Diun doesn't send notifications about new images found

[mlazzarotto]

I've deployed Diun v4.26.0 on 3 Docker hosts.
Diun succesfully finds new images but doesn't even try to send a notification via Pushover.
Running diun notif test succesfully send a Pushover message.

Logs

Host 1

Sun, 04 Feb 2024 17:54:44 CET INF Starting Diun version=v4.26.0
Sun, 04 Feb 2024 17:54:44 CET INF Configuration loaded from 10 environment variable(s)
Sun, 04 Feb 2024 17:54:44 CET INF Cron triggered
Sun, 04 Feb 2024 17:54:44 CET INF Found 6 image(s) to analyze provider=docker
Sun, 04 Feb 2024 17:54:47 CET INF New image found image=docker.io/fireflyiii/data-importer:latest provider=docker
Sun, 04 Feb 2024 17:54:47 CET INF New image found image=docker.io/fireflyiii/core:latest provider=docker
Sun, 04 Feb 2024 17:54:47 CET INF New image found image=docker.io/library/alpine:latest provider=docker
Sun, 04 Feb 2024 17:54:47 CET INF New image found image=docker.io/freshrss/freshrss:latest provider=docker
Sun, 04 Feb 2024 17:54:47 CET INF Jobs completed added=5 failed=0 skipped=0 unchanged=1 updated=0
Sun, 04 Feb 2024 17:54:47 CET INF Cron initialized with schedule 0 */6 * * *
Sun, 04 Feb 2024 17:54:47 CET INF New image found image=docker.io/portainer/agent@sha256:558676e1e8a019023ec2d9fe10644e82c5ee12405694841098e2f429552a5e48 provider=docker
Sun, 04 Feb 2024 17:54:47 CET INF Next run in 5 minutes 35 seconds (2024-02-04 18:00:22.732194923 +0100 CET)

Host 2

Sun, 04 Feb 2024 17:55:42 CET INF Configuration loaded from 10 environment variable(s)
Sun, 04 Feb 2024 17:55:42 CET INF Starting Diun version=v4.26.0
Sun, 04 Feb 2024 17:55:42 CET INF Cron triggered
Sun, 04 Feb 2024 17:55:42 CET INF Found 2 image(s) to analyze provider=docker
Sun, 04 Feb 2024 17:55:44 CET INF New image found image=docker.io/portainer/agent@sha256:558676e1e8a019023ec2d9fe10644e82c5ee12405694841098e2f429552a5e48 provider=docker
Sun, 04 Feb 2024 17:55:44 CET INF Jobs completed added=1 failed=0 skipped=0 unchanged=1 updated=0
Sun, 04 Feb 2024 17:55:44 CET INF Next run in 4 minutes 22 seconds (2024-02-04 18:00:07.114836182 +0100 CET)
Sun, 04 Feb 2024 17:55:44 CET INF Cron initialized with schedule 0 */6 * * *

Portainer Stack

compose

version: "3.5"

services:
  diun:
    image: crazymax/diun:latest
    command: serve
    volumes:
      - "diun_data:/data"
      - "/var/run/docker.sock:/var/run/docker.sock"
    env_file:
      - stack.env
    labels:
      - "diun.enable=true"
    restart: always

volumes:
  diun_data:

environment variables

TZ=Europe/Rome
DIUN_WATCH_WORKERS=20
DIUN_WATCH_SCHEDULE=0 */6 * * *
DIUN_WATCH_JITTER=30s
DIUN_PROVIDERS_DOCKER_WATCHBYDEFAULT=true
DIUN_PROVIDERS_DOCKER=true
DIUN_NOTIF_PUSHOVER_TOKEN=redacted
DIUN_NOTIF_PUSHOVER_RECIPIENT=redacted
DIUN_NOTIF_PUSHOVER_TEMPLATETITLE={{ .Entry.Image }} {{ if (eq .Entry.Status "new") }}is available{{ else }}has been updated{{ end }}
DIUN_NOTIF_PUSHOVER_TEMPLATEBODY=Docker tag {{ if .Entry.Image.HubLink }}[**{{ .Entry.Image }}**]({{ .Entry.Image.HubLink }}){{ else }}**{{ .Entry.Image }}**{{ end }} which you subscribed to through {{ .Entry.Provider }} provider {{ if (eq .Entry.Status "new") }}is available{{ else }}has been updated{{ end }} on {{ .Entry.Image.Domain }} registry (triggered by {{ .Meta.Hostname }} host).

[mlazzarotto]

I've got a notification for a new image today, so I deleted the diun container and I recreated but I didn't get the same notification...

[mlazzarotto]

Notification are working fine, but I supposed that Diun would notify on first run.