n8n Schedule Trigger not firing? How to monitor your workflows
When an n8n workflow fails, you can be told. When its Schedule Trigger never fires, there is no run, so there is nothing to tell you. Here is how to check the usual causes and how to get alerted on both cases.
Updated
Short answer
Make sure the workflow is saved and published, and check which time zone it uses. To get alerted when a run is missed, add an HTTP Request node at the end of the workflow that pings a heartbeat URL. If the ping does not arrive on time, the workflow failed or never started.
Monitor your n8n workflows freeWhy an n8n workflow stops running
Start with the Schedule Trigger node itself. These are the settings the n8n docs point to.
| Cause | How to check | Fix |
|---|---|---|
| Workflow not published | The workflow was saved but never published, or was unpublished | Save and publish it. The Schedule Trigger node needs a published workflow |
| Time zone | The run happens at a different hour than you expected | The node uses the workflow time zone if one is set, otherwise the instance time zone. Set it in the workflow settings, or self-hosted, set GENERIC_TIMEZONE |
| Changed interval or variable | You edited the schedule or a variable it uses and the run times did not move | Unpublish the workflow and publish a new version. Variables are read only when the workflow is published |
| Invalid cron expression | A Custom (Cron) rule shows a parse error | Check the syntax against the n8n cron examples, or test the expression on crontab.guru |
| Month has no such day | A Months rule set to the 31st skips shorter months | Pick a day every month has, or use a Custom (Cron) expression |
| Interval counted from publish time | Seconds and Minutes rules run at even intervals measured from when you published | Use a Custom (Cron) expression if you need fixed clock times |
If none of these fits, the n8n instance itself may be down or restarting. That is the case you cannot see from inside n8n at all.
Why an Error Workflow does not catch it
In Workflow Settings you can pick an error workflow. n8n runs it when an execution of that workflow fails.
A schedule that never fires creates no execution, so there is nothing to fail and the error workflow stays idle. The same goes for an instance that is down: it cannot run an error workflow either.
Add a heartbeat ping to the end of the workflow
A heartbeat monitor waits for your workflow to check in. You give it the expected interval. If the check-in is late, you get an alert, whatever the reason.
- Create a Heartbeat monitor in UptimeIO and copy its URL (see the last section).
- In your workflow, add an HTTP Request node after the last step that does real work.
- Set Method to
GETand paste the heartbeat URL into URL. - Open the node options, add Timeout, and enter a value in milliseconds, such as
10000. The node then gives up after 10 seconds instead of waiting. - Save and publish the workflow again.
| HTTP Request setting | Value |
|---|---|
| Method | GET |
| URL | https://heartbeat.uptimeio.com/heartbeat/YOUR_HEARTBEAT_TOKEN |
| Options → Timeout | 10000 |
Connect the node only on the success path. If an earlier node errors and stops the run, the ping node never executes, and the missing ping is your alert.
To send details such as how many items were processed, set Method to POST and send a small JSON body.
Catch failures that do run with an Error Trigger
A failed run can tell you which node broke, which a missing ping cannot. Set this up once and reuse it.
- Create a new workflow that starts with the Error Trigger node. An error workflow must start with it.
- Add a node that notifies you, such as email or Slack, and include the data the trigger provides: the execution ID, the error message and the last node executed.
- In each workflow you want covered, open Workflow Settings and choose this workflow as the Error Workflow.
One error workflow can serve several workflows. The execution URL and ID are only included when the execution is saved in the database. You cannot test an error workflow by running the failing workflow manually, so trigger a real failure to try it.
To make a run count as failed when the result is wrong but no node errored, add a Stop And Error node on that branch. It forces the execution to fail, which then triggers the error workflow.
Pick an interval and grace period
Set the monitor interval to match the schedule: 15 minutes for a workflow that runs every 15 minutes, 24 hours for a daily one. The grace period is how late the ping can be before you are alerted. The ping is sent at the end of the run, so it has to cover how long the workflow takes.
| Workflow | Interval | Grace period |
|---|---|---|
| Syncs every 15 minutes, takes under 1 minute | 15 minutes | 5 minutes |
| Daily report at 08:00, takes about 5 minutes | 24 hours | 30 minutes |
| Hourly import, takes about 10 minutes | 1 hour | 20 minutes |
Set it up in UptimeIO
- Create a monitor and choose the Heartbeat type.
- Set the interval and grace period.
- Copy the heartbeat URL into the HTTP Request node as shown above.
- Choose where alerts go: email, Slack, Telegram, Pushover or a webhook.
Heartbeat monitors are on every plan, including Free. A few details worth knowing:
- Intervals: 1 minute to 24 hours, with a grace period of 1 second to 24 hours. The shortest interval is 5 minutes on Free and 1 minute on Pro and Scale.
- Requests: GET or POST, no authentication. A POST can carry a small JSON object, such as how long the run took.
- Incidents: an incident opens when a ping is late, and resolves after 3 on-time pings in a row.
Questions
- Why is my n8n Schedule Trigger not firing?
- Check that the workflow is saved and published, that the workflow or instance time zone is what you expect, and that a schedule built from a variable was re-published after you changed the variable. The n8n docs list these in the Schedule Trigger node page.
- Why did my Error Workflow not run?
- An error workflow runs when an execution of the workflow fails. If the schedule never fires there is no execution, so nothing runs. Use a heartbeat ping to catch missed runs.
- How do I get an alert when an n8n workflow fails?
- Create a workflow that starts with the Error Trigger node and sends you a message, then select it as the Error Workflow in the settings of each workflow you want covered.
- How do I monitor an n8n workflow that runs on a schedule?
- Add an HTTP Request node at the end of the workflow that sends a GET request to a heartbeat URL. The monitor alerts you when the request does not arrive within the interval plus grace period.
- Can I monitor n8n workflows on the Free plan?
- Yes. Heartbeat monitors are on every plan. The shortest interval is 5 minutes on Free and 1 minute on Pro and Scale.
Related
- AI agent monitoring - Heartbeat checks for scheduled agents and LLM jobs.
- Cron job monitoring - How UptimeIO heartbeat monitoring works and which plans include it.
- Cron job not running - Find why a scheduled job stopped and get alerted when it happens.
- Heartbeat monitoring docs - Settings, ping examples, metadata, and rate limits.
- Pricing - Plan limits and prices.