Your n8n Failure Alert Never Fired: Test the Pager, Not Just the Workflow
Your n8n Failure Alert Never Fired: Test the Pager, Not Just the Workflow 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. The review queue nobody was watching I had done the responsible things. Deferred jobs lived in a real queue, not in execution…
The article discusses the importance of testing both the workflow and the alert system in n8n, rather than relying solely on alerts. The author explains that they had implemented a workflow with multiple safeguards, including a deferred job queue, a sweeper to handle stale claims, and an alert system using the n8n workflow-failure trigger.
Despite these measures, the author found forty jobs sitting in the review queue for several days without triggering an alert, which indicates that the alert system had failed in two separate ways. The first failure was due to subscribing to the wrong signal, where the alert only fired when a workflow failed, but a job landing in review is not considered a failure.
The second failure was caused by the channel itself, such as a rotated Slack webhook token or an archived channel. The author emphasizes the importance of testing delivery at the destination and keeping the alert path separate from the watched system to ensure its reliability.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
