Know when it stops

Build-along · ~30 min at your own keyboard

An automation that stops will not tell you. It just stops, and you find out three weeks later. These are the usual causes. A sign-in or token expires. A column, file or folder is renamed. A usage limit is hit. The input changes format. The AI output drifts and gets worse. A run succeeds with an empty output. The cure is a heartbeat. A heartbeat is a separate check, on its own schedule, that looks for the output and alerts you when it is not there by a set time. It does not trust the job to report its own failure. Then test it. Break the job on purpose, and confirm that the alert fires. An alert you have never seen fire is a guess.

Ladder · Level 4The long version: Automation ↗

Your starter: Failure drill

Checklist

Make it yours: Answer each line for your own job. Cross out the failures that cannot happen to it, and add the one that worries you most.

FAILURE DRILL: [job name]

Can this happen to my job? (yes, no or maybe, and what it would look like)
[ ] The sign-in or connection expires:
[ ] A file, folder, sheet or column is renamed:
[ ] A usage limit is hit:
[ ] The input arrives in a new format:
[ ] The output slowly gets worse:
[ ] The run says success but the output is empty:

HEARTBEAT (a separate check, never inside the job)
Checks: [the exact place and name of today's output]
Alerts when: no output, or an output with nothing in it
Deadline: [a time after the job should finish, with a margin]
Alerts me by: [the channel I see fastest]
Alert says: "[job name] did NOT run today"

BREAK IT ON PURPOSE
What I broke, and the time:
When the alert arrived, and what it said:
What I fixed, and the next clean run:

The coach checks that what you paste back is your own work. The starter pasted back unchanged won't pass.

Do this

0/7

Checkpoints

▸You should now see a heartbeat check that runs on its own schedule, separate from the job.
▸You should now see an alert in your phone, email or calendar from a day you broke the job on purpose.
▸You should now see the job working again, and no alert, after the fix.

The three ways this goes wrong

The alert never fires when you break the job. — The heartbeat is looking in the wrong place or runs before the job should finish. Check where the output lands, check the label or name it looks for, and move the deadline later. Break the job again.
The alert fires every day, even when the job works. — The heartbeat looks for the wrong name, or the deadline is before the job finishes. Match the name exactly and move the deadline later.
The job ran but made an empty output, and no alert fired. — Your heartbeat only checks that a run happened. Change it to check that the output has content, such as at least one draft or one row with today's date.

Dated facts in this lesson: ChatGPT has Scheduled Tasks (chatgpt.com/schedules). Workspace agents are on Business and Enterprise plans (researched Oct 4, 2026, not yet confirmed by a person: check the source before you rely on it); Claude scheduled tasks live in Cowork, under 'Scheduled' in the sidebar. They run in the cloud with your laptop off, on Pro and above (researched Oct 4, 2026, not yet confirmed by a person: check the source before you rely on it); Gemini Spark (beta) has Schedules: time-based, Gmail monitors and topic monitors. It is on AI Pro and Ultra, for personal accounts only, with up to 50 schedules. An older 'Scheduled actions' feature allows 10 active (researched Oct 4, 2026, not yet confirmed by a person: check the source before you rely on it); Microsoft 365 Copilot automates through Copilot Cowork and Power Automate. A scheduler in consumer Copilot is not confirmed (researched Oct 4, 2026, not yet confirmed by a person: check the source before you rely on it); Grok has Automations (daily, weekly and email triggers) on a paid tier (researched Oct 4, 2026, not yet confirmed by a person: check the source before you rely on it); Perplexity has Scheduled Tasks that run at most once an hour (researched Oct 4, 2026, not yet confirmed by a person: check the source before you rely on it).

Share what happened

Paste: (1) the six failure modes and which ones your job can have, (2) the heartbeat rule: what it checks, when, and how it alerts you, (3) what you broke on purpose and when, and (4) the alert that fired, with the time it arrived.

Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].

🔒 Don't paste confidential, personal-health, or payment info.