BLOG · 2026-06-23
My automation stopped working and nobody noticed
The worst automation failure isn't the one that throws a red error and pings you. It's the one that fails in silence: it just stops doing its job, nobody gets any alert, and you find out weeks later when a customer asks about something that never arrived.
What a silent failure is
An automation is a robot that does a task for you: copy an order into a sheet, send a confirmation email, sync two apps. While it works, you forget it exists. And that's exactly the problem: when it stops working, you also forget it exists.
That's a silent failure: the robot stalls or starts doing its job wrong, but it doesn't shout. To you everything looks normal, because you stopped watching that task — that's the whole reason you automated it.
An example of the kind that hurts
Picture a shop that automated this: every new order gets copied to a spreadsheet the warehouse uses to prepare shipments. It worked for six months. One day, the spreadsheet provider changed something under the hood and the connection stopped writing. Orders kept coming in, customers kept paying, but the warehouse was looking at a sheet that no longer updated. Three weeks later, the avalanche of "where's my order?" arrived.
Nobody did anything wrong. They simply trusted that "no alert means it's fine." That's almost never true.
Why it happens
- An outside service changed. Your automation talks to other apps (your website, your email, your bank, your CRM). If one of them changes, your robot is left talking to itself.
- A password or permission expired. Many connections renew themselves periodically. If one fails to renew, the automation can no longer get in.
- Something odd arrived. An order with a strange character, an empty file, a malformed date — and the robot, which only knows what you taught it, gets stuck.
- The credit ran out. If the automation uses a paid service (email sending, AI, SMS) and the plan runs dry, it just stops running.
The golden rule: get alerted when NOTHING happens
Here's the mindset shift. Most people set up alerts for when there's an error. But a silent failure, by definition, produces no error. The fix is the opposite: make the automation tell you "I'm still alive" every day. If one day it goes quiet, you know something's wrong.
It's the same as a heartbeat. Hearing the beat doesn't worry you — losing it does. In the technical world this is literally called a heartbeat, and it's the difference between finding out the same day or three weeks late.
The minimum you should have
- A daily heartbeat. Every important automation sends a "done" signal somewhere you actually look (a Slack channel, a summary email, a dashboard). No signal = go check.
- A results counter. If it processed 40 orders yesterday and 0 today, that's an alarm even if there's no technical error.
- A named owner. "The automation alerts" is useless if the alert lands in an inbox nobody reads. It has to reach a specific person.
How we approach it
When we build custom automations, we start from a simple idea: an automation with no monitoring is a polite time bomb. So every process we ship carries its own heartbeat and counter, and alerts a real person when the rhythm changes. It's not an add-on: it's part of the job. Automating something and not watching it is like putting the car on autopilot and stepping out of the seat.