Short answer: a scheduled task in the Claude desktop app runs on your computer. If the computer is asleep, or the app is closed, at the scheduled time, the task does not run, and the run history shows it as skipped. Nothing is broken. The task has no computer to run on. The fixes are: keep the machine awake, move the task to a cloud schedule, or give Claude a computer of its own.
What the run history is telling you
People who set up Cowork or Claude Desktop scheduled tasks for business work (a 7:30am report, a daily inbox pass, a Monday brief) keep running into the same wall. One user's run history said *Skipped* next to the 7:30am task after the laptop slept overnight. Another counted 16 scheduled tasks going dark five times in one week, every time because of their own machine: the app closed after a restart, the Mac went to sleep, a login screen sat there until morning.
The pattern is the same every time:
- The task fires only while the Claude app is open and the machine is awake.
- A task that uses a local folder also needs that folder's machine to be on.
- If the moment passes, the task is skipped. It does not catch up later.
So the question is not "why did Claude fail?" It is "what was Claude supposed to run on at 7:30?"
Fix 1: keep the machine awake
The cheapest fix. On a Mac: System Settings → Energy (on a laptop, Battery → Options), and turn on "Prevent automatic sleeping when the display is off". Keep the lid open: a closed MacBook stays awake only with power and an external display connected. A terminal caffeinate -i keeps the system from idling while it runs; apps like Amphetamine do the same with a menu-bar switch. The Mac sleep guide has the details. Keep the Claude app open, and keep yourself logged in.
Trade-offs: a laptop that never sleeps and never travels, a session that still dies on an update or a reboot, and a login screen after a restart that stops everything until you type a password. If the task matters on a Tuesday when you are away, this is fragile.
Fix 2: move the task to a cloud schedule
Anthropic also offers scheduled work that runs in its own cloud rather than on your machine. If your task is a self-contained prompt with no local files, that removes the laptop from the equation. Check Anthropic's current documentation for what those runs can access and how many you get on your plan; the limits change.
Where people report it falls short: the run does not carry files or memory from last week's run, it cannot read a folder on your computer, and run counts are capped. A task that needs "compare this week with last week" or "update the spreadsheet in my Documents folder" is hard to move there.
Fix 3: give Claude a computer of its own
The third option is the one a server admin would pick: run Claude on a small computer that is always on, and schedule the task there. The laptop can sleep, travel, or be replaced. The 7:30 task runs at 7:30. Files and notes from the last run are still on that computer for the next one.
That is what a Podway pod is: a small always-on computer in the cloud with Claude Code on it. You give it the job in plain words ("every weekday at 7:30, pull the numbers and write the brief"); it sets the schedule on its own machine, keeps its files between runs, and you steer it from the Claude app on your phone. It uses your own Claude Pro or Max plan; Podway does not resell tokens. The pod costs from $4 a month, and the first one is free with no card needed.
A quick checklist before you change anything
- Open the task's run history. "Skipped" means the machine or the app was not available; an error means something else.
- Check what the task touches: a local folder, a connected account, nothing local.
- Nothing local, and a simple prompt → try the cloud schedule first.
- Needs local files or memory between runs → keep the machine awake, or give the task its own computer.
- Needs to run while you travel → its own computer.
If option 3 fits, start a free pod and give it the task that got skipped this morning.