TL;DR
- When an automation stops, you don't get an error. Something just stops showing up, and that doesn't appear on any dashboard.
- It happened to us: a nightly task left no file on eight nights between August 17 and October 11. Each time, another task found the gap when it went looking.
- ChatGPT's own help page says it in writing: a scheduled task can pause for reasons as ordinary as deleting the chat it came from.
- The fix is a signal with an owner: a visible trace, the time it should show up, a named person who expects it, and what they do the first day it doesn't arrive.
- Your move: write those four lines for the automation you'd least want to lose for a week. Ten minutes.
The short answer. No complaints doesn't mean an automation still works. When one stops, there's no error. It just stops delivering, and nothing on your screen changes. It happened at Hub365 AI on eight nights between August and October, with one of our own tasks. Ten minutes per automation covers it: a visible sign that it ran, the time it should appear, and a named person waiting for it.
Your automations probably work almost all the time. That's the trouble: the things that almost always work are the ones we stop checking.
Two weeks ago we wrote about the report that says "nothing new": a check that showed up on time and said "nothing" when there was something. This one comes a step earlier, and it's harder to spot: the report that never shows up, when nobody's assigned to expect it.
1. An automation that stops doesn't make a sound
Think about a newspaper delivered to your door. If it's missing one morning, you notice before your first coffee, because you look for it at the same time. If nobody in the house reads it, it could stop coming for a month and nobody would say a word.
Automations work the same way, except almost nobody looks for them. The appointment reminder the day before. The WhatsApp message that asks for a review two days after each job, like the one in the 5-star review system.
Your customer won't miss a message they didn't know was coming
When an automation doesn't run, a message goes missing, and the only person who could notice is the one it was meant for. But that customer never knew it was coming. They forget the appointment or skip the review, and in your numbers it looks like a slow week, not a breakdown.
What nobody expects, nobody misses.
2. Ours went missing on eight nights, and another task told us
Every night at nine, one of our automated tasks reads the sources we follow and writes a file of content ideas. It's the same task from the "nothing new" story, with a different problem: on some nights it wrote nothing.
The nights on record:
- Monday, August 17; Wednesday, August 19; and Thursday, August 20.
- Wednesday, September 30.
- Wednesday, October 7.
- Friday, October 9; Saturday, October 10; and Sunday, October 11.
Not one of those eight nights produced an alert. Every time, the next task went to read the file and logged that it was missing. The August ones turned up in that week's summary, which found a single daily file where there should have been several.
One more miss came from the task that builds that weekly summary. It was due Friday, October 9, and ran Monday the 12th, around 1 p.m. The summary itself records when it was made.
We haven't diagnosed the cause yet. What the record does show is how we found out.
A task went looking for it. No person was assigned to expect it
The uncomfortable part isn't that a task failed. Everything fails sometimes. It's that over eight nights, no one person was in charge of noticing. When the file was there, we read it in the morning. When it wasn't, nobody had it written down as their problem, and the only thing looking for it on a schedule was another automated task. An automated task reads whatever it finds. When it finds nothing, it writes that down and moves on.
The longest gap ran from Friday through Sunday, and what found it was the weekly summary that ran late, on Monday the 12th. For those three days, nobody had checking written down as their job.
3. ChatGPT's own help page says a task can stop
We're not quoting ChatGPT's help page to single out one tool. We're quoting it because it's in writing, and it shows how a task can stop without anyone touching it.
When we read that page on October 16, 2026, it said a task may pause if it's inactive, if it needs you to do something, or if the chat it belongs to is archived or deleted. And if it needs your approval for something, it pauses until you review it.
Clearing out old chats on a Sunday and deleting the one that created the task is enough to pause it. If you set yours up after reading how to get ChatGPT and Gemini working while you sleep, that's worth knowing.
The same page shows where task notifications live: Settings, then Notifications, as a push alert, an email, or both.
The page doesn't say whether you get notified when a task pauses. We don't know either, so we wouldn't build the fix on it.
A "done" alert only helps if someone notices the day it doesn't come
If your tool has an alert like that, switch it on. But on the day the task doesn't run, nothing arrives, and only someone expecting it at a certain time will notice. The alert is half the fix; the other half is a person.
4. The fix: a signal with an owner
The fix fits on a sticky note: four things written next to each automation that matters, and all four are decisions, not research. A month ago we wrote that a list with no name and no date isn't a plan. Here the name does a different job. It belongs to whoever notices that something didn't happen, not whoever does the work.
1. Does it leave a trace you can see every time it runs? A "done" email, a new row in a sheet, a sent message, a file stamped with today's date. Fix: write down which one, in a single line. If you can't find one, ask whoever set it up: "Where do I see that it ran?"
2. Do you know what time that trace should show up? "Mondays before nine." "Two days after each job." "Every night." Without a time, nobody can tell that something is late or missing. Fix: write the time next to the trace.
3. Is one specific person waiting for it? One person. Not "the team," not "the system." Fix: write their name down, and tell them.
4. Does that person know what to do the first day it doesn't arrive? One line: "I'll do it by hand that day and message whoever set it up." Fix: write that line under the name. If the automation lives in a tool that lists paused tasks, that first step starts with looking there.
With all four answered it can still fail, but the first day it does, somebody knows, long before eight nights pile up.
Our nightly task had two of the four
The trace was there: the day's file. So was the time: nine p.m., written down in the task's own record.
What was missing was a name. When the file was there, we read it, but the only thing looking for it on a schedule was another automated task, not a person. And with no name, there was no first step either: nobody had written down what to do on a morning when the file wasn't there.
The signal existed. Nobody was waiting for it.
5. Where the four lines stop
The four lines won't stop a task from pausing. They shrink the time between the pause and the moment someone sees it, from weeks to one morning.
They also won't tell you whether what arrived is right. That was the "nothing" report from two weeks ago.
When a person did the job, their absence showed up on its own
In automating a broken process does not fix it, it speeds it up we explained why a process gets automated only after it works in a person's hands. That order has a side effect almost nobody notices: while a person does the job, a missed day is obvious, because someone is missing. Automate it, and with that person goes the only natural way of noticing that something didn't happen. A signal with an owner puts back, on purpose, what you lost when you automated.
So whose job was it? Naty and Todd
Naty: What bothers me most about our case isn't that the task failed. It's that it was missing for eight nights, and nothing in our notes says either of us caught it before the next task did. We read it when it was there. When it wasn't, it wasn't anybody's job.
Todd: That part can be decided the day it gets built. Next to what the automation does, write down who would miss it if it didn't run one day. If the answer is nobody, that's the first fix.
Naty: My first job was at a dive shop, and six months in I was running the whole operation. That's where I learned the system matters more than talent. This case adds something to that: a system nobody is waiting on stops getting looked after, and nobody ever decides to let it slide.
Todd: You can test it without waiting for a failure. Some ordinary morning, ask the person waiting for it whether yesterday's arrived, and when. If they answer right away, someone really is waiting for it.
The one thing to do this week
One automation, one note, ten minutes.
- Pick the automation you'd least want to lose for a week without knowing. Just one.
- Write its four lines. If you don't know the trace, ask whoever set it up, today.
- Next time it's due to run, have that person check that the trace arrived. If it didn't, you know on day one, not night eight.
To close
Trace, time, name, first step: four lines that cost nothing, written next to every automation that matters. The time says when to look, and the name says who looks. We had the time written down, and nobody in charge of looking.
Start with one today. When it fails, and someday it will, you'll know in time.
If you can't find the trace for one of your automations, bring it to a call and we'll track it down together. It's free.
And if you want one practical AI move a week, no hype: subscribe to The AI Edge.
Thanks for reading all the way down. May the next missed delivery get caught before the coffee's ready.
Keep reading
- The report that says "nothing new" is the first one to check - when the report does arrive, and says "nothing"
- Automating a broken process does not fix it, it speeds it up - run it by hand before you automate it
- ChatGPT and Gemini Can Now Work While You Sleep (Here's How to Set Them Up) - how scheduled tasks get set up
- The 5-Star Review System - the WhatsApp review request on autopilot
- Your Business Has More Doors Open Than You Are Counting - the name as the person who closes what's still open
- Scheduled tasks in ChatGPT, OpenAI Help Center - why a task can pause, and where its notifications are set
Sources
- OpenAI, "Scheduled tasks in ChatGPT," OpenAI Help Center, accessed October 16, 2026 - reasons a scheduled task pauses, and task notification settings - https://help.openai.com/en/articles/10291617-scheduled-tasks-in-chatgpt
