Why Your Business Automation Stopped Working

When a business automation stopped working, the most likely cause is not a fault in the software. It is a login that quietly expired. The connection between two of your tools depends on a signed-in session, that session has a lifetime, and when it ends nothing crashes and nobody is told. The work simply stops happening while every screen still looks normal. A two-minute check once a week catches it, and that check is worth more than any amount of troubleshooting after the fact.

The important part is the distinction: a tool that is logged out is not a tool that is broken. They look identical from the outside and they need completely different responses.

Why does an automation stop without telling you?

Because nothing went wrong. An error is an event — something tried, something failed, something somewhere gets a red message. An expired session is the absence of an event. The thing that should have run did not run, and silence is not an alarm.

This is the part owners find hardest to believe, and it is the whole problem. You are watching for a failure, and what actually happens is nothing at all.

A login expired, not a system failed

When you connect your booking system to your calendar, or your till to your accounts, you are not joining two programs together permanently. You are granting one of them a key to the other, and that key has an expiry date. Sometimes it is thirty days, sometimes six months, sometimes it ends the moment somebody changes a password. After that the automation keeps asking politely and keeps being refused.

The screen that still looks right

The dashboard still loads. The rules you set up are still listed. The tool still says it is connected, because it was connected the last time anyone asked. Nothing in the interface is designed to shout that the last successful run was three weeks ago, and almost nobody scrolls to find out.

What actually breaks the connection between two business apps?

Four causes account for nearly all of it, and none of them is a bug.

Somebody changed a password

Usually for a good reason — a prompt, a scare, a new phone. Changing a password ends every signed-in session on that account, including the ones you forgot were sessions: the tool that posts for you, the one that pulls your sales in, the one that files your invoices. The person who changed it has no way of knowing which quiet jobs they just stopped.

Somebody left

If the connection was set up under one person’s account, it dies with their account. This is the same weakness as a password nobody else knows, and it is why the connections in a business should sit on an address the business owns rather than on a named individual.

The permission needed renewing

Access granted to a third-party app is usually time-limited by design, and for good reason — the NCSC’s small business guide treats reviewing who has access as basic hygiene rather than an advanced step. The side effect is that a connection you set up last year may already have lapsed without anyone revoking anything.

The card on the tool in the middle failed

A subscription in the chain lapses, that tool drops to a free tier, and the feature your automation depends on quietly turns off. The email about the payment went to whoever set it up, which may be nobody who still reads it.

How do you check in two minutes a week?

You do not check whether the tools are running. You check whether the work happened. That is a different question and a much faster one.

Pick the three or four jobs in your business that nobody watches — the ones that are supposed to happen without a person — and for each, name one thing you can see with your own eyes that proves it ran. Then look at those things once a week, at a fixed time, in the same order.

Bookings into the calendar: open the calendar, not the booking system. Is yesterday’s appointment in it?
Sales into the accounts: open the accounts. Does the most recent transaction have the right date?
Enquiries into the inbox: send yourself one from the website form. Did it arrive?
Scheduled posts, reminders, reports: look at the place they land, not the place they are configured.

Two minutes, once a week, because you are glancing at four end results rather than auditing four systems. It is worth running the same check on who still has access to your accounts at the same time — Google’s security checkup lists the apps connected to yours in one page.

Write down what proves it ran

The check only survives the week you are busy if it is written down. Four lines, one per job: what should happen, and where you look to see that it did. Anyone in the business can run it, which is the point — this should not be a thing only you can do.

What this cost us, honestly

We run our own marketing on an AI setup that writes and publishes without anybody approving each item. On the evening of 1 October it published nothing. The posts were written, the schedule ran, and the tool that does the actual posting had been signed out of the browser it works in. There was no error, no warning email, no red mark anywhere. We found out by looking at the account the next morning and seeing an empty day.

Nothing was broken. Nothing needed fixing. Somebody needed to sign back in — which took about fifteen seconds and would have taken fifteen seconds a day earlier, if anybody had looked. That is the entire lesson, and it is why the check exists rather than a better alerting system. An alert can only fire on an event, and the event here was a non-event.

We build automations for other businesses and this still caught us, which should tell you how little it has to do with technical skill.

FAQ

How do I tell the difference between logged out and broken?

Try to do the thing by hand, as yourself. If it works when you do it manually, the software is fine and the connection is not — it is an access problem. If it fails for you too, then something is genuinely broken and it is worth reporting.

Can I just set up an alert instead?

Only partly, and it is worth understanding why. Good automations can be built to report when they succeed rather than only when they fail, so that silence itself becomes visible. But many off-the-shelf tools cannot do that, and a connection that has lost its access often cannot send you anything at all — including the warning.

Whose account should the connections live on?

An address the business owns, not a person’s own login, and with the password recorded somewhere the business can reach. Connections set up under a personal account end when that person does.

How far back should I look when I find one has stopped?

Further than you want to. Work out the last date the job definitely ran, then check what was supposed to happen between then and now — unsent invoices, unlogged sales, enquiries nobody answered. The gap is usually older than the day you noticed.

Does this get better with a custom-built system?

The expiry does not go away, because it is a security feature rather than a flaw. What changes is who is told. A system built for you can be made to report its own successes, re-authenticate on a schedule, and name the person to contact when it cannot.

Where this leads

Most businesses do not need more automation before they need to know whether the automation they already have is running. The weekly check costs nothing and tends to find at least one thing on the first go. When you do decide to build something new, this is one of the questions worth asking the person building it: how will I know, without being told, that it worked today? We build workflow automation with that question answered up front, and if you have a job that may or may not have run this week, tell us what it is and we will tell you what proof of it is worth building in.