Oriel — AI & technology worth noticing, every day.

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

Post · https://dev.to/sarvar_04/i-lost-half-a-day-to-an-n8n-workflow-that-was-working-it-never-ran-43p

An n8n error workflow fires only when an execution fails. Unpublish a workflow and nothing runs, so nothing fails, so no alert. Here is the liveness check I run on EC2.

First seen by Oriel on .

AI summary

The article shows why n8n error workflows miss workflows that stop running and builds a scheduled API check to detect unpublished, missing, failing, or stale workflows.

  • The author observed zero new executions during 150 seconds after unpublishing a one-minute schedule workflow; executions resumed after republishing.
  • A Python monitor checks workflow existence and publication status, the latest execution result, and whether a successful run falls within a configured freshness window.
  • It recommends read-only API scopes, alerting only when state changes, and retaining successful execution data long enough for freshness checks.
  • An in-n8n monitor cannot detect its own outage, so the article recommends an external heartbeat; the author had not yet wired or measured this layer.
  • The test stack used n8n 2.43.6, PostgreSQL 16, and Mailpit; PostgreSQL 16 received compatibility-only support, with PostgreSQL 17 or newer recommended for fresh installs.

#n8n #workflow monitoring #postgresql #site reliability

Generated by gpt-5.6-sol. Check the original for details.

Metric trends

Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained

Reactions

Total public reactions reported by the source; distinct from points and likes.

  • DEV Community: 30, latest observation ; +18 over observed period since

Comments

Comment count reported by the source.

  • DEV Community: 32, latest observation ; +32 over observed period since

Aliases

SourceExternal IDURL
DEV Community4966488https://dev.to/sarvar_04/i-lost-half-a-day-to-an-n8n-workflow-that-was-working-it-never-ran-43p Read discussion