Run it while you are not watching

Build-along · ~25 min at your own keyboard

A job that only runs when you press a button is not automated. Most assistants now have a built-in scheduler. You save a prompt, set a time, and it runs on its own. The proof is a result with a timestamp that you did not trigger. Set the schedule, then walk away. When you come back, look at the run history. Check the time on the result. The first run often reveals a problem: the tool was not connected, the input was not where you said, or the output went somewhere you did not expect. That is why you run it a few times before you trust it.

Ladder · Level 4 gateThe long version: Automation ↗

Your starter: Scheduled job prompt

Prompt

Make it yours: Replace every bracketed line with the details from your job card. Keep the rules. Add one rule that only your job needs.

You are running a scheduled job for my business. Nobody is watching while it runs.

READ: [the one place the input lives: a named sheet, folder or inbox label]
LOOK FOR: [which items count, for example rows older than three days with no reply]
FOR EACH ITEM: [what to do, in one or two plain steps]
MAKE: [the output, for example one draft per item, or one summary]
PUT IT IN: [the exact place: a named label, folder or sheet tab]
SOUND LIKE: [two or three words on tone, or "my saved instructions"]

RULES
- Write drafts only. Do not send, post, delete or pay for anything.
- Do not invent prices, dates or names that are not in the input.
- If an input is missing or empty, say so at the top and make nothing. Do not guess.
- End with one line: how many items you found and how many you made.

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 saved scheduled task with a prompt, a time and a repeat setting.
▸You should now see a run in the history with a timestamp that you did not start by hand.
▸You should now see the real output of the run in the place your job card says it lands.

The three ways this goes wrong

The task does not run at the set time. — Check what the scheduler needs: the app open, the laptop awake, the right account signed in, the connector turned on. Check the time zone in the schedule. Then set it for a few minutes ahead and wait again.
The run says 'completed' but the output is empty or wrong. — The input was not found. Open the run and read it. Fix the file name or connection in the prompt. Keep the line 'If an input is missing, say so at the top.'
You clicked 'run now' and it worked, but you are not sure the schedule works. — A hand-started run proves nothing about the schedule. Set a new run a few minutes out and do not touch it. Capture that run's timestamp.

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) your saved prompt, (2) the schedule setting (time, repeat, where it runs), and (3) a run from the history with its timestamp and a sample of the output. Say that you did not start that run by hand.

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

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