Colour theme

Problem A08

My automation broke and I did not find out until someone complained.

Last updated Prices and terms last checked
How this page is funded

No link on this page is an affiliate link. We are in the programme below, so we could earn a commission elsewhere on this site — but not from anything on this page. We recommend free tools where they are the better answer, including ones that earn us nothing.

  • Make.com: 35% of subscription payments for 12 months; extra-operation purchases do not earn commission (terms verified 2026-09-24)

What you are doing now

You assume it is working. Days later you discover it has not been, and you reconstruct by hand what was missed.

How often: Occasional, but it is the single biggest reason people abandon automation.

What you want instead

A failure notifies a human immediately, retries where it is safe to do so, and leaves a record of exactly what did not run.

The free option first

A manual weekly spot-check costs nothing and is genuinely the right answer for low-stakes workflows.

Who should not do this

Nobody should skip this. If a workflow matters enough to build, it matters enough to know when it stops.

How to stop this happening

Every item below exists because we measured the failure it prevents, not because it is general advice.

Before you build anything for this, the Automation Decision Sheet works out whether it is worth automating at all. It is free, needs no email address, and often concludes that it is not.

Workflows we built and ran for this

Problems that usually come with this one