Why business automations break, and who fixes them

Building an automation is the easy part. The day it goes live, it works. Everyone is happy.

Then, six weeks later, it stops. Or worse, it keeps running and quietly gets things wrong. Nobody notices until a customer, a supplier or the accountant does.

This isn't bad luck. Every automation connects to things that change without asking you. This guide covers the common reasons automations break, the kind of break that is hardest to spot, and the real question behind all of it: who fixes it?

The five reasons automations break

1. A website or system changes

Your supplier redesigns their portal. Your accounting software moves a button. A government site changes how it lists notices. An automation that reads or clicks through a website depends on that website staying the same, and websites don't.

2. A login expires or a password changes

Most automations sign in to your tools on your behalf. When someone changes a password, leaves the company, or a connection simply expires, the automation is locked out. It usually fails with an error nobody reads.

3. The input changes shape

A supplier sends their invoice in a new layout. A customer replies in a voice note instead of text. A colleague adds a column to the spreadsheet. The automation was built for the old shape, so it either stops or, more dangerously, reads the wrong thing.

4. Another app changes how it works

The apps your automation connects to update all the time. Usually nothing breaks. Sometimes a field gets renamed or a feature is retired, and the step that depended on it fails.

5. Your business changes

A new branch opens. A price list changes. You start selling in a new market. The automation is still doing exactly what you asked six months ago, which is no longer what you need.

The break that's hardest to spot: it ran, but it was wrong

A loud failure is annoying, but at least you know about it. The expensive kind is the quiet one, where the automation finishes every day and the result is wrong.

• An invoice amount is read from the wrong line after the supplier changes their layout.
• A reminder goes out with last month's price.
• A report runs on schedule but leaves out the new branch.

A green tick that says "completed" tells you the automation ran. It doesn't tell you the result was right. That's why checking only for errors is not enough. Someone has to compare the output with what correct looks like.

Who fixes it?

This is the question most people skip when they choose a tool. There are three usual answers.

Your own team. With a do-it-yourself tool like Zapier, Make or n8n, the person who built it is the person who fixes it. That works while they have the time and stay in the role. When they're busy, on leave or gone, the automation becomes a thing nobody understands.

A freelancer or consultant. Someone builds it for you and hands it over. Fixes are a new job each time: you notice the problem, get in touch, wait, and pay for the hours.

A done-for-you service. The people who built it keep it working as part of the service. They watch every run, so they usually find the break first.

How Scribe.sg keeps a workflow working

Scribe.sg builds, runs and maintains AI workflows for small businesses. Keeping them working is the main part of the job, not an extra. Here is what happens today:

1. Every run is watched. We log each run of every workflow.
2. Small blips are retried automatically. A slow website or a brief outage usually clears up on the next try.
3. Real failures come to our team. When something actually breaks, we're alerted, not you.
4. We find the cause and fix it. That might be a changed website, an expired login or a new invoice layout.
5. We test the fix on real work before it goes live. We run the fixed workflow again on the work that failed and check the result is right, not just that it finished.
6. We tell you what happened. In plain language: what broke, and what we changed.

For anything that touches money or patient records, a person checks the result before a fix goes live.

If you only remember one thing

Before you automate anything, ask: when this breaks, who will notice, and who will fix it? If the answer is "probably me, eventually", the automation will cost more than its price.

If you'd rather build it once and have someone else keep it working, book a 30-minute call. Tell us what your team retypes, and we'll tell you honestly whether we can take it off your hands.

Further reading: what done-for-you automation actually means and how we watch every run.