Why this matters
Your renewal risk pass works. Now it has to happen every Monday for two years, including the Mondays you are on holiday, the Monday your laptop is in a bag, and the Monday you forget it exists.
Most courses say "now schedule it" and move on. We stay, because the interesting question is what happens on the week it does not run, and how you would ever know.
What you will be able to do
- State what scheduling in this product is, and what our fact base cannot tell you about it.
- Run a pre-flight check that establishes which execution mode applies to you, and record it.
- Write the four-question failure plan before creating any schedule.
- Design a cadence-plus-check substitute for an event trigger, and state its detection latency.
What scheduling is, and the part that is unresolved
What it is: you describe a task once and Claude runs it on a recurring basis or on demand, delivering reports, briefings and summaries. For a weekly risk list, exactly the shape of the job.
Now the honesty, because you are about to make a business promise on top of it: our fact base carries an unresolved conflict about how scheduled tasks execute.
- One reading, from post-July 2026 sources: scheduled tasks run remotely, so they run on their cadence even when your computer is asleep or the desktop app is closed.
- The other, older reading: tasks execute only while the computer is awake and the desktop app is running.
The likely resolution is that the second describes pre-July local execution and the first describes post-July cloud execution. That is unverified, and this course will not assert it.
Whichever applies to you, one claim our fact base does make plainly: scheduling is convenience automation and should not be treated as a reliable mechanism for tasks that must run at an exact time without fail.
You are going to find out yourself: the answer for your machine, your plan and your build is the only one that matters, and a pre-flight you ran beats a sentence you read in a course.
Try this now The pre-flight check.
1. Schedule a trivial task: write the current date and time to
ops/heartbeat.md, once a day.
2. Note the scheduled time, and the date you set it up.
3. Close the desktop app. Put the machine to sleep. Leave it.
4. After the scheduled time has passed, open ops/heartbeat.md.
5. Record in ops/scheduled-tasks.md: execution mode observed, the date you
verified it, what you did (app closed, machine asleep), and the result.
6. Re-run this check after any app update, and re-date the entry.
It takes elapsed time, not work time: start it at the beginning of Part A of LAB-08, the exercise sheet in labs/LAB-08 of your practice pack (start with its README), and read the result at your next session. And record the result even if it is inconvenient. A missing output teaches you more: your reporting depends on a machine being awake, and that belongs in the register and the rollout brief.
The failure plan: four questions before the schedule exists
Mandatory for every scheduled revenue task. Answer in writing, in the register, before you create the schedule.
| Question | Why it is the question |
|---|---|
| 1. How would I know it did not run? | Failure here is silent. There is no error in your inbox. |
| 2. What breaks downstream if it does not run? | This is the one that decides whether the workload belongs here at all. |
| 3. What is the manual fallback, and how long does it take? | If you cannot answer this in minutes, you do not have a fallback, you have a hope. |
| 4. What is the maximum acceptable delay? | Turns "it should run weekly" into a number somebody can be held to. |
The rule: if the answer to question 2 is "the business", this workload does not belong on a schedule you cannot guarantee. A commission run, a billing file, a regulatory submission, a customer-facing report with a contractual deadline: none of those. They go where a guaranteed scheduler lives, and L8.4 tells you when to move.
What does belong here: the weekly risk list, the Monday movement pack, the monthly hygiene audit. Work where a day late is an inconvenience and a human notices the absence within the acceptable delay, because you built something that makes them notice.
No event triggers, and the pattern that replaces them
There is no inbound email address and no native "when a deal moves to Stage 3, run this". This is the sharpest architectural limit in the product for revenue work, and the clearest boundary between this tool and a workflow engine or CRM automation.
The substitute is cadence plus check:
1. Run on a cadence.
2. Save the state you observed, dated, in 30-output/state/.
3. Next run, compare current state against the saved state.
4. Act on the difference. Save the new state.
That gives you "tell me when this changes", with a lag. The lag is called detection latency, and it is a number you choose and accept in writing:
| Cadence | Detection latency | What that means on a Friday afternoon |
|---|---|---|
| Daily | up to 1 day | Friday change seen Saturday |
| Weekdays only | up to 3 days | Friday change seen Monday |
| Weekly, Mondays | up to 7 days | Friday change seen the following Monday |
| Monthly | up to 31 days | Do not use this for anything with a renewal date in it |
Write it in the register in this form: "A renewal date passing without a renewal opportunity is detected within 7 days. The maximum exposure is a renewal that lapses on a Tuesday and is seen the following Monday."
Then the honest alternative, said out loud to whoever asked: if that latency is unacceptable, the trigger belongs in the CRM or a workflow engine. Wrong tool for the trigger, not for the analysis: keep the analysis here and put the trigger where triggers work.
The register entry
Write it in ops/scheduled-tasks.md, before the schedule is created; a seed register is at templates/M8/scheduled-tasks.md in your practice pack. This is the artifact.
| field | value |
|---|---|
| Task | Weekly renewal risk list |
| Brief | 20-briefs/renewal-risk.brief.md |
| Cadence | Mondays, 07:00 local |
| Output | 30-output/retention/renewal-risk-YYYY-MM-DD.md |
| Positive run signal | Appends a dated line to 50-runs/RUN-LOG.md on every run, |
| | including runs that flag nothing |
| Execution mode | Verified 2026-08-06: app closed and machine asleep overnight, |
| | output present next morning. Re-check after any app update. |
| Detection latency | Up to 7 days. A renewal date passing with no renewal |
| | opportunity is seen at the next Monday run. |
| How I would know it did not run | Monday routine: check that RUN-LOG.md has a |
| | line dated this week. Absence of the line, not absence of an alert. |
| What breaks if it does not run | One week of delay on a risk list. Nothing |
| | contractual, nothing customer-facing, no SLA. |
| Manual fallback | Run the brief by hand. 12 minutes measured on 2026-08-06. |
| Max acceptable delay | 7 days. Beyond that, escalate to the CS lead. |
| Owner | <name> |
Note the "positive run signal" row. The report writes a line every time it runs, including the weeks it finds nothing. That one design choice makes the next section possible.
Tell these apart: ran and found nothing, or did not run
In your inbox, your folder and your week, these two are identical. Nothing arrived.
It ran and found nothing
50-runs/RUN-LOG.md
## 2026-08-03 renewal risk pass
Accounts evaluated: 102 scored, 87 live customers
Renewal dates in the next 150 days or past: 47 (8 past, 39 upcoming)
Newly flagged this week: 0
Still flagged from previous weeks: 12
Field profile step 0: pass, no owner range anomaly
Exceptions: 3 accounts, no usage rows
Run completed 07:04
Zero new flags, and the log proves 102 accounts were evaluated to produce that zero. This is a result. You can act on it, quote it, compare it to next week.
It did not run
50-runs/RUN-LOG.md
## 2026-07-27 renewal risk pass
Accounts evaluated: 102 scored, 87 live customers
Newly flagged this week: 1 (ACC-03107)
Run completed 07:03
That is the last entry. Nothing for 2026-08-03, nothing for 2026-08-10. The output folder holds renewal-risk-2026-07-27.md and nothing newer. Two weeks in which nobody was told anything about the renewal book, and nobody noticed, because a report that finds nothing and a report that does not exist feel the same: a quiet inbox.
The difference is only visible if the report emits a positive signal on every run. Absence produces no evidence of itself; you manufacture the evidence, then build a habit of looking for it.
What honest feedback on this looks like
Here is the response a learner receives when their register's "how I would know it did not run" row reads: "I would notice, because I would not get the report."
That answer describes exactly the situation in which you will not notice.
In week one the report runs, evaluates 102 accounts, flags nothing: nothing arrives. In week two it does not run at all: nothing arrives. Your detection mechanism is "nothing arrived", which cannot tell them apart. The two are the same observation.
The failure of a scheduled report is silent. No error, no red mark, no retry notice. The absence is the error, and absence generates no signal by itself.
What would have caught it. A positive run signal: a dated line appended to
50-runs/RUN-LOG.mdevery run, including runs that flag nothing, plus a Monday routine that checks last week's line exists. You are then looking for the presence of something rather than the absence of something, which a human can actually do. Stronger still: write a dated file every run even when the findings are empty, so a gap in the filenames shows at a glance.What to change. Two rows of your register: "Positive run signal" becomes a real mechanism, and "How I would know it did not run" names the check, the person, and a cadence. Then answer question 2 again, honestly. If "what breaks if it does not run" was serious, ask whether this workload belongs on a schedule you cannot guarantee at all.
One thing you got right, worth keeping: you did not claim the product would alert you. It will not, and a register that assumed it would is a worse artifact than one with a weak detection habit.
When this goes wrong
The break. Schedule the renewal risk report. Then reproduce the run that does not happen: check for the output where the register says it should be, on a day when your recorded pre-flight conditions are not met. If your pre-flight found local execution, that is any day your machine was asleep at the scheduled time. If it found remote execution, use the lab's file-based stand-in.
The tell. Nothing in the output folder, and nobody noticed. That is the entire tell. No error, no notification. The report simply did not appear, in a week where an unremarkable report also would not have appeared, on a Monday when you were busy.
The cost in the shipped scenario is concrete: the renewal risk pass is what would have surfaced ACC-03043, whose renewal date passed on 2026-07-28 with no renewal opportunity on the record. Two missed runs is two more weeks in which the only person who knows is the CSM who wrote it in a call note in April.
The guard. Two parts, and neither works without the other.
- The positive run signal: a dated line in
50-runs/RUN-LOG.mdon every run, including empty ones, and a dated output file even when the findings are empty. - The habit that reads it: your Monday routine checks that last week's line exists. Put it in the register as a named person and a named check, not an intention.
Worth knowing: the general lesson transfers to every scheduled thing you will ever build. Detecting absence requires a positive signal, because absence produces none. Every monitoring system you have ever admired is built on that sentence.
What you keep
ops/scheduled-tasks.md, the register, with one complete row: cadence, output location, execution mode as verified with the date, detection latency accepted, positive run signal, the four-question failure plan, and an owner. This is the module's signature artifact.- A cadence-plus-check design with its latency written as a sentence.
Check yourself
- Four candidate workloads for a schedule: (a) the Monday pipeline pack; (b) the monthly hygiene audit; (c) the quarterly commission statement file that finance sends to payroll on the 3rd; (d) the weekly renewal risk list. Which one do you reject, and name the reason in the product's terms.
- Your manager asks for an alert when any account's health score drops below the threshold. Design the substitute and state the latency you are accepting.
- A scheduled report has produced no output for three weeks and nobody noticed. Name the likely cause classes, then name the thing that actually failed.
- Somebody proposes removing the run-log line "because it is noise when there is nothing to report". Answer in two sentences.
Where this goes next
L8.4 covers the remote surface, writes the rollout brief a manager approves, and names the conditions under which a workflow should leave this tool entirely.