What to Do When Automation Goes Wrong

This is the lesson people skip

You have set something up, it works, and the temptation is to stop thinking about it. That is the entire point of automating, after all. Skip this lesson and the ending writes itself: in about four months you will discover that a routine you trusted has been wrong since March.

Automation does not usually fail with a bang. It fails politely, in a way designed not to attract your attention.

The three ways it goes quiet

It just stops. A file gets renamed, a permission changes, a workspace gets tidied up by someone helpful. The routine fails and you notice nothing, because the absence of a Monday summary looks identical to a Monday when you were too busy to read it. Missing things are almost impossible to spot. Your brain does not raise an alarm about an email that did not arrive.

It keeps running on stale assumptions. Worse, and far more common. Your weekly chase list still references a spreadsheet that was superseded in April. Your client summary still describes a contact who left. Nothing errors. It produces a confident, well formatted, entirely obsolete document every single week, and you skim it and nod.

It drifts past its usefulness. Your job changed, the project ended, the client left. The routine still runs, still lands, and is now pure noise. Noise trains you to ignore the channel, which means the day something genuinely important appears there, you will scroll past it.

Make the routine report on itself

You will not remember to audit your automations. Nobody does. So build the audit into the output, where you cannot miss it.

Add this to the top of every run, before anything else.
HEALTH LINE

Which sources you actually used, by name.
When each was last updated.
How many items or how many pages you read.
Whether anything changed since the previous run.
Then these rules.
If a source is missing or unreadable, reply with SOURCE MISSING plus the name,
and produce nothing else.
If a source has not changed in 30 days, add STALE and the date.
If you had to guess or infer anything, list it under ASSUMED.
Never fill a gap silently.

Three lines at the top, and silent failure becomes loud failure. That is the single highest value change in this whole course.

Keep a human in the loop where it counts

Not everywhere. A weekly summary you read yourself already has a human step, which is you reading it. The place to be strict is anything that leaves your desk or that someone else will act on.

The rule of thumb: if the output goes to another person, is used to make a decision, or touches money, dates, commitments or a named individual, a human reads it first. That human is you, it takes thirty seconds, and it is the cheapest insurance available.

The monthly ten minutes

Once a month, on a date you will actually keep, look at your routines. Not the output, the routines themselves.

Here are the recurring tasks I have set up, with what each produces.
Take me through them one at a time and ask me these four questions.

Did this actually run and land every time this month? Yes or no.
Did I read it, or skim and ignore it? Be honest.
Is every source it depends on still current, correctly named and still mine
to access?
Is the reason I set this up still true?
Then tell me which ones to keep as they are, which to rewrite,
and which to switch off entirely. Recommend switching something off if I have
admitted to ignoring it.
MY ROUTINES:
[list them]

Question two is uncomfortable and important. A routine you skim is a routine you have already stopped trusting. Fix it or kill it, but do not let it keep landing.

Know the off switch before you need it

The last piece, and it takes two minutes. When you set up any routine, find out how to pause it, edit it and delete it, and try each one once while the stakes are zero. Wherever your scheduled or recurring tasks are listed you should be able to see what exists and stop any of it, though the exact wording and location vary and do move about.

The reason to rehearse it is that the day you need the off switch is a day when something is going wrong and you are already flustered. That is a bad moment to be searching a menu.

For each routine I have set up, write me a short note I can keep.
WHAT IT DOES: one line.
WHAT IT TOUCHES: the files, folders or people involved.
WHEN IT RUNS: day and time.
HOW TO STOP IT: where I go to pause or delete it.
WHAT BREAKS IF IT STOPS: what I would have to do by hand instead.
WHO ELSE SEES THE OUTPUT: names, or NOBODY.
Keep it under six lines each. This is a note for a bad Tuesday,
not documentation.