[SUPPORT] Timed Events not working

[qrgprepper]

Describe your question or issue
I created 2 timed events and it's not working and I don't know if I missed some configuration but it looks correct.

Environment (please complete the following information):

• Host OS: Windows (wsl ubuntu 24.04)
• MeshMonitor Version: lastest
• Deployment Method: Docker Compose
• Docker/Container Version (if applicable): [e.g., v1.2.3]

Configuration
Please share relevant configuration files (remove any sensitive information):
docker-compose:
services:
meshmonitor:
image: ghcr.io/yeraze/meshmonitor:latest
container_name: meshmonitor
ports:
- "8080:3001"
restart: unless-stopped
volumes:
- meshmonitor-data:/data
# Mount local scripts directory for Auto Responder scripts
- ./scripts:/data/scripts
environment:
- TZ=America/Sao_Paulo
- MESHTASTIC_NODE_IP=192.168.1.228 # Change to your node's IP
- ALLOWED_ORIGINS=http://localhost:8080 # Required for CORS
- MESHMANAGER_URL=http://meshmanager:8000
- NODE_ENV=development
- ENABLE_VIRTUAL_NODE=true
- VIRTUAL_NODE_PORT=4404

AI Responder - AI-powered mesh assistant

Credit: https://github.com/LN4CY/ai-responder

ai-responder:
image: ghcr.io/ln4cy/ai-responder:sha-b45e0442f554960a8a270d9b7d1b4e7cbffe630d
container_name: meshmonitor-ai-responder
restart: unless-stopped
environment:
- INTERFACE_TYPE=tcp
- MESHTASTIC_HOST=meshmonitor
- MESHTASTIC_PORT=4404
- AI_PROVIDER=gemini
- ADMIN_NODE_ID=!node_id
- ALLOWED_CHANNELS=0
- GEMINI_API_KEY=****
volumes:
- ai-data:/app/data
depends_on:
- meshmonitor

volumes:
meshmonitor-data:
driver: local
ai-data:
driver: local

I also have a blank .env file.

Logs
Please provide relevant log output:
There are no logs (success or error)

Screenshots
this one runs a python script

this one is text only:

What have you tried?
I tought about the timezone so I set the tz on docker-compose.yaml but it did not change anything.

Additional context
Add any other context, error messages, or information that might be helpful.

[Yeraze]

Hi! Thanks for the report. Timer triggers are working in our testing, so let's debug what's happening in your setup.

The timer scheduler only starts after the node successfully connects (you should see a log line like ⏱️ Scheduled timer "..." with cron: ... when it starts). If the node connection drops and reconnects, the scheduler restarts automatically.

Can you check the following?

1. Look for scheduler startup logs — search your container logs for ⏱️:

   docker logs meshmonitor 2>&1 | grep "⏱️"

   You should see lines like:

   • ⏱️ Scheduled timer "name" with cron: ... — means the timer was scheduled
   • ⏱️ Timer "name" triggered — means the cron fired
   • ⏱️ No timer triggers configured — means the setting wasn't saved

   If you see nothing at all, the node may not have connected.

2. Verify your cron expressions — from your screenshots, what cron expressions did you set? The format is * * * * * (minute, hour, day-of-month, month, day-of-week). For example:

   • Every 5 minutes: */5 * * * *
   • Every hour at :00: 0 * * * *
   • Daily at 8 AM: 0 8 * * *

3. Check that triggers are enabled — make sure the toggle is ON (green) for each trigger.

4. Verify node connection — check that your node shows as "Connected" on the dashboard. The timer scheduler won't start until the node connects.

Please share the output from step 1 and we can narrow down the issue!

[Yeraze]

Those two events are set to run at 6am and 9am, is that what you expect ?

[qrgprepper]

@Yeraze yes, I expect them both to run
Yesterday the first one was executed at 6am but today it did not.

Here's the log:

I was reading the logs and I found this one:
[NODE-CRON] [WARN] missed execution at Wed Mar 25 2026 06:05:00 GMT-0300 (Brasilia Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.

[Yeraze]

Thanks for the logs — that's very helpful!

The key line is:

[NODE-CRON] [WARN] missed execution at Wed Mar 25 2026 06:05:00 GMT-0300 (Brasilia Standard Time)! Possible blocking IO or high CPU user at the same process used by node-cron.

This is a known limitation of node-cron — it runs in the same Node.js event loop as MeshMonitor. If the server is busy at the scheduled time (running database queries, processing traceroutes, auto-announce, security scans, etc.), the cron tick gets blocked and the execution is skipped.

What likely happened: At 6:05 AM, MeshMonitor was in the middle of a heavy operation (possibly auto-traceroute scheduling, security scanning, or database maintenance) which blocked the event loop long enough for node-cron to miss the tick.

Workarounds for now:

1. Avoid scheduling timers at the same time as other automated tasks (auto-announce, auto-traceroute, maintenance)
2. Stagger your timer cron expressions by a few minutes (e.g., 7 6 * * * instead of 5 6 * * *)

We'll look into making timer execution more resilient — potentially by using a separate worker thread or adding missed-execution recovery.