Vivere

n8n

A Schedule Trigger that stops firing produces no failed execution, so your Error Workflow never reports it. Here is the check that does.

An Error Workflow fires when an execution fails, which means an execution has to exist first. A Schedule Trigger that does not fire produces no run at all, so nothing fails, and the notify node you put on the error branch has nothing to report. It covers a workflow that ran and broke. It cannot cover a workflow that never started.

That happens in three common shapes. The instance was restarting, redeploying or being updated at the scheduled minute, and n8n neither catches up the missed run nor records that one was skipped. The workflow was not active, after an import, a restore from a backup, or a cluster of trigger errors that switched it off. Or the trigger is firing on a timezone or a cron expression that is not the one you are thinking in, so the run lands at an hour nobody is watching. The full list runs to six.

If you already check with a second workflow

The usual hand-built answer is a second Schedule Trigger on a deliberately different cadence, looking for the row the daily workflow should have written today. That is a good design, and the different cadence is the right instinct, because a restart that lands on one schedule is unlikely to land on both.

The gap in it is where it runs. Both workflows are timers inside the same n8n process, so a host that is off, a deploy that hangs, or a container that does not come back takes the checker away along with the thing it was checking. The rest of this page is that same check, run from outside your instance.

Add an HTTP Request node as the last step

  1. Add an HTTP Request node after the final node of the scheduled workflow.
  2. Method POST, URL https://vivere.dev/p/<monitor-id>.
  3. Optional: under Body choose Raw, content type text/plain, and send an expression such as {{ $json.summary }} to keep it as the run log.
  4. Set Settings → On Error to Continue so a ping failure never fails the workflow.

Report failures from the Error Workflow

The Error Workflow still earns its place for the runs that do happen and break. Add an HTTP Request node to https://vivere.dev/p/<monitor-id>/fail with the error message as the body, and the monitor goes Down at once with the message attached rather than waiting out the deadline.

Monitor settings

Use the same schedule as the trigger. A workflow on Every hour is period 1h, grace 10m. A cron schedule such as 0 6 * * 1-5 should be entered as a cron expression on the monitor, with the instance's timezone.