Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Why Automations Stop Working, and How to Notice
Business Automation

Why Automations Stop Working, and How to Notice

Why automations decay through changed systems, processes and silent failure, and how monitoring, a named owner and annual reviews keep them working.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Automations decay through changed source systems, changed business processes and unnoticed silent failure. Monitor for volume anomalies and zero output, name an owner, and review annually against what the business actually does now.

Three ways automation decays

  1. The systems around it change. A supplier alters an API, a form gains a field, a report changes format.
  2. The business changes. The process the automation encodes is no longer how work is done, so it produces correct output for the wrong workflow.
  3. It fails silently. Nothing errors; it simply stops producing, or produces empty results, and nobody notices for weeks.

The third is the most dangerous and the easiest to guard against.

Monitor for absence, not just errors

The most under-implemented alert in business automation is “this produced nothing today and it usually produces forty”. Errors get alerted; silence does not, and silence is what actually happens.
  • Volume outside the expected range for the day of week
  • Zero output where output is normal
  • Runtime much shorter than usual, which often means it did nothing
  • Downstream systems not receiving what they expect

Name an owner

Every automation needs someone who cares whether it still does the right thing. Not who maintains the code — who owns the outcome.

Unowned automations run for years after they stopped being useful, or stop being useful without anyone deciding.

Review annually against reality

  1. Does this still reflect how we do the work?
  2. Is the output still used by someone?
  3. What exceptions are being handled manually that could now be automated?
  4. What has changed upstream that we have not accounted for?
  5. Should this still exist at all?

The last question matters. Automations that no longer serve a purpose still consume maintenance and still fail occasionally.

Keep the documentation with the automation

What it does, why it exists, who owns it, what it connects to, and what to do when it fails. A paragraph, kept current, saves days when something breaks and the person who built it has left.

The most expensive automation failure is one nobody understands well enough to fix.

Budget for maintenance

Ten to twenty per cent of build cost annually is a reasonable allowance. Automations connecting to third-party systems sit at the higher end, because the other side changes on its own schedule.

Businesses that budget nothing end up with automations they no longer trust, which is worse than not having them.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

How often do automations break?

Ones connecting to third-party systems, perhaps a few times a year. Self-contained ones can run for years untouched. The number of integrations is the best predictor.

What if the person who built it has left?

Documentation and a named business owner are what protect you. Without them, the first failure becomes an investigation rather than a fix.

Should we rebuild old automations?

Only if they are failing frequently or blocking something. Working automation that is unfashionable is still working automation.

How do we know if an automation is still used?

Ask the owner, and check whether the output is opened or the downstream system is consuming it. Both are usually easy to verify and occasionally surprising.

Keep reading

More on Business Automation

Start here

Automations running that nobody watches?

A short review will tell you which could fail silently and which no longer match how you work. We do this for systems we did not build.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →