Menu

1 / 11

I lost half a day to an n8n workflow that was "working." It never ran.

DEV Community: aws·Sarvar Nadaf·16 days ago
#tf1Ghx8b
#devtoaws#devto#dev#workflow#error
Reading 0:00
15s threshold

Last month I lost half a day to a workflow that was working perfectly. It just was not running.

An order-sync job on my self-hosted n8n had been switched off during an unrelated edit. No red execution. No error email. The dashboard was calm. The only reason I found it: someone asked why a downstream report looked stale.

That is the gap. Nearly every monitoring guide for n8n starts with an error workflow. An error workflow is good at one job, and only that job: it fires when an execution fails. It does nothing when an execution never starts.

This post is about that second case, the one most setups never alert on. I will show you why your error workflow is blind to it, then build a small liveness check that catches it, and I tested the whole thing on a production-shaped stack: n8n 2.43.6 on PostgreSQL 16 on an Amazon Linux 2023 EC2 box. Not the default SQLite demo. The same shape you actually run.

This is a follow-up to my earlier post on securing self-hosted n8n on AWS .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.