all systems MULHERN hire me
System · Hardened

n8n Rescue and Audit

Two production workflows that looked green and quietly weren't. Turned into boring, provable reliability.

Hardenedn8nretriesdedupmonitoringsecretsHardened July 2026
BEFOREhealth check: green0 rows writtentoken refresh times out5-hour silent gapAFTERretry x3 on all 9 HTTP nodesidempotent dedup (seen-map)alert on ANY errored run / 24hsecrets rotated + gated
Before and after: from false-green monitoring to provable reliability.

The job

A green health check sitting on top of a dead pipeline is the worst failure mode there is. A shallow ping was reporting success while the workflow wrote zero rows for hours.

The build

Retry policies on all 9 HTTP nodes so transient timeouts stop becoming outages. Idempotent dedup so retries never double-process. Service names instead of hardcoded IPs so a reboot is a non-event. A health check rewritten to alert on any errored execution in 24 hours. Secrets moved out of workflow JSON and rotated.

What it proves

This is what an audit actually finds: retries, dedup, false-green monitoring, and hardcoded assumptions. The fixes are unglamorous and they are the whole job.

Retry policies on all 9 HTTP nodes closed a 5-hour data gap caused by a token-refresh timeout. The health check now flags any errored execution in 24 hours instead of reporting green while writing zero rows.
Zero silent failures
since the rebuild
Build me one like this