Marketing automation

Automation audit: finding what quietly broke

By Yulia Hrytsenko 3 min read
Automation audit: finding what quietly broke

Automations break quietly: the workflow doesn’t error, it simply stops firing. A quarterly four-step audit — register, silent-failure check, duplicate hunt, run-cost review — finds that before a customer does.

The root cause is that automations get created and never maintained. After a year a typical team is running a dozen or more workflows, half of which nobody has looked at since the day they were built.

Step 1: what belongs in the register?

A list of every active workflow with three columns: what it does, what triggers it, who owns it.

That sounds bureaucratic and produces the biggest return: most teams don’t have such a list, and the act of compiling it surfaces workflows everyone had forgotten.

  1. 1

    What it does

    In one business-language phrase: «sends an email after purchase», not «webhook → filter → action».

  2. 2

    What triggers it

    An event or a schedule. Duplicates by trigger become visible immediately.

  3. 3

    Who owns it

    A named person. A workflow with no owner is the first candidate for disabling.

  4. 4

    Last verified

    The date it was last checked. An empty cell is itself an audit finding.

Step 2: how do you find silent failures?

A silent failure is a workflow that’s formally active but never fires: a field was renamed, an access token expired, the platform removed a method.

The fastest check is the date of each workflow’s last successful run. Anything that hasn’t fired for longer than its normal interval is suspect.

Step 3: clear duplicates and legacy

Group by action rather than by name. The classic finding: two workflows sending a similar message to the same customer because different people built them at different times.

The second classic finding is workflows tied to tools you no longer use. They do no harm but consume your plan’s allowance and complicate every future audit.

The safe removal rule: disable, wait a month, then delete. If nobody noticed in a month, the workflow genuinely wasn’t needed.

Step 4: how do you price your runs?

Automations bill by runs or actions, and the invoice grows invisibly. This is where the audit literally pays for itself.

What to look for:

Workflows with an over-eager trigger. Firing on every record change instead of once a day is the classic reason a bill tripled with no new automations.

Redundant steps in a chain. Under per-action billing every step costs money. A ten-step workflow where three are intermediate transformations can be shortened.

Runs with no outcome. A workflow fires a thousand times a month and in nine hundred cases exits at «condition not met». Move that filter closer to the trigger.

Quarterly audit checklist
  1. Build or refresh the register: action, trigger, owner, date verified.
  2. Check each workflow’s last successful run date.
  3. Separately check infrequent workflows (monthly, quarterly).
  4. Group by action and find duplicates.
  5. Disable ownerless workflows; delete after a month.
  6. Find the three most expensive by run count and inspect their triggers.
  7. Manually walk two or three key workflows end to end.
  8. Record the audit date in the register.

Frequently asked questions

  1. 01 Why audit automations that appear to work?

    Because the dangerous failures are silent: the workflow doesn't error, it just stops doing anything. You usually find out from a customer, a week or a month after it broke.

  2. 02 How often should you audit?

    Quarterly is enough for most teams. More often only makes sense after big changes — a CRM switch, a site rebuild, a new channel — because that's when workflows break most.

  3. 03 Where does an audit start?

    With a register: every active workflow, what it does and who owns it. Most teams don't have one, and half the audit's findings surface simply while compiling it.

  4. 04 How do you find duplicates?

    Group workflows by action rather than by name. The classic finding is two workflows sending a similar message to the same customer, built by different people at different times.

  5. 05 What about workflows nobody remembers?

    Disable rather than delete, and wait a month. If nobody notices, delete. It's the safest way to clear legacy without breaking something that turns out to matter.