The Workflow That Paged Me 47 Times: Deduplicating n8n Failure Alerts
This is part of my build-in-public series on running LLM workflows in n8n in production. Everything here is from real templates I sell and support β the mistakes are mine, the fixes are tested.
Forty-seven pages, one failure
One night a provider went down, and my phone paged me forty-seven times. Not forty-seven failures. One failure, retried and re-alerted until the provider came back up in the morning.
Each retry produced a new execution, each execution hit the same dead provider, and each one fired its own alert. By page twelve I had stopped reading them. By page thirty I had muted the channel. The real failure β the one I needed to act on β was buried under forty-six copies of itself, and the morning's first genuine new failure arrived into a channel I had already learned to ignore.
The alerting had done exactly what I asked it to do: tell me when a run fails.β¦