Why Did My n8n Workflow Stop Running Without Any Error?
Because nothing failed. An n8n error workflow only fires when an execution fails, and a workflow that never started creates no execution at all. The usual causes are a deactivated workflow, a schedule trigger lost in a restart, or a timezone mismatch. You need a check that notices when an expected run is missing.
What actually causes it?
Error workflows only react to runs that exist. Four things stop the run existing.
- The workflow was left inactive after an import, restore or deploy script, and looks fine in the editor.
- A schedule trigger did not reload after a restart or upgrade, and the only evidence is in the container logs.
- The Schedule Trigger follows the workflow timezone, then the instance one, so your 06:00 job now runs at 06:00 somewhere else.
- Memory kills and timeouts on a small VPS fail randomly enough to be dismissed as flukes.
What should I check first?
Open Executions for the workflow and check when the last run happened. Whether it succeeded matters less. A green execution from eleven days ago on a daily schedule is a failure wearing the colour of a success. Then confirm the workflow is active and compare the workflow and instance timezones.
What do I do about it this week?
- List every scheduled or webhook workflow with how often it should run.
- Compare each one's last execution against that interval. Anything overdue is already broken.
- Make each critical workflow write a timestamp on every successful run.
- Have a monitor outside n8n alert when a timestamp is older than twice the interval. A monitor inside the same instance dies with it.
What should I avoid?
- Do not treat "no alerts" as good news, because a healthy estate and a deaf one look identical from the dashboard.
- Do not give your error workflow its own error workflow, because failures can loop.
- Do not wait for someone to notice. That someone is usually a customer, weeks later.
Related questions
Does n8n Cloud solve this?
Partly. Cloud removes restarts and memory limits, but a deactivated workflow or a timezone mismatch behaves the same anywhere.
Is this unique to n8n?
No. Zapier, Make and Salesforce scheduled Flows share it. Most monitoring only watches for runs that failed.
Keep reading
- The automation audit finds the manual work and the unmonitored jobs already running in your estate.
- Rules or AI automation covers the related question of whether a process needed a model in the first place.
- Can a consultant build n8n workflows for clients without a paid license? answers the licensing question before you hand a client an n8n setup.
- Automated website uptime monitoring is the same detection idea applied to a site rather than a workflow.
- AI-assisted Google Ads reporting is an n8n build where a missed run would have gone unnoticed for a month.
We build and maintain this kind of monitoring as part of workflow automation and system integration work, usually after being called in to explain why something stopped three weeks ago.