Your Schedule Trigger missed a run, and n8n will not catch it up
The container restarted, the host rebooted, or a deploy landed at 03:00 — and the 03:00 run simply never happened. Nothing failed, so nothing was reported: the execution list just has a hole in it.
Schedule Trigger fires on a timer inside the running process. If the process is not up at that instant, the tick is not queued for later — it is lost. n8n has no backfill, and because no execution ever started, there is no failed run to alert on. Silence looks identical to success.
Stop trusting the clock as the record. Make the job idempotent and driven by state: read what is still pending (a `processed_at IS NULL` query, a cursor, a since-timestamp) instead of assuming 'the last hour'. Then a missed tick costs nothing — the next run picks up the gap. For jobs that truly must run at a time, add an external heartbeat (a cron monitor that expects a ping) so a missing run raises an alarm instead of nothing.
Stop n8n over a scheduled window on purpose, start it again, and confirm the next run processes the skipped work and the monitor flagged the gap.
Not sure if this is the only leak?
Paste your workflow and see which of its jobs lose work when the clock is missed — free, 30 seconds.
Scan my workflow free