Why didn't my Claude Cowork scheduled task fire this morning?

The most common cause is that Claude Desktop was not running at the scheduled time. Anthropic's own documentation states scheduled tasks only fire while the computer is awake and the Claude Desktop app is open. If your laptop slept, Claude Desktop quit, or you closed the lid before the task time, the task is silently skipped — no notification, no retry. The fix is an always-on host.

Do Claude Cowork scheduled tasks fire when the desktop app is open but on a different tab?

In current versions, no. Multiple GitHub issues confirm that Cowork scheduled tasks may not execute at their scheduled time if Claude Desktop is open but focused on a regular chat view instead of the Cowork tab. The task only fires when you manually return to Cowork. This is a known bug being tracked at github.com/anthropics/claude-code.

What are the 5 most common causes of Claude scheduled task failures?

1) Computer asleep or off at scheduled time. 2) Claude Desktop quit, crashed, or not launched after reboot. 3) Cowork view not active (Claude Desktop open but on a different tab). 4) Cron syntax error in the schedule definition. 5) Expired Anthropic session token (resign every 30 days). The first three are solved by an always-on host running Claude Desktop 24/7.

How do I make Claude Cowork scheduled tasks fire reliably?

Move Claude Desktop to a machine that never sleeps — a Mac mini left plugged in at home, a Windows mini-PC, or a managed cloud desktop. The cloud desktop is the most reliable because data centers have backup power, redundant internet, and automated OS update handling. Standby (https://trystandby.com) provides this as a managed service starting at $39/month with an Always-On Guarantee.

Can I run Claude Cowork on a Linux server to fix scheduled task reliability?

No. Claude Cowork requires Claude Desktop, which is Windows and macOS only. There is no Linux build. The Anthropic API runs on Linux but does not include Cowork or scheduled task features. The correct fix is a Windows or macOS cloud desktop.

Will my scheduled task fire if my laptop is in sleep mode at the scheduled time?

No. Sleep mode suspends all processes including Claude Desktop. The scheduled task is silently skipped and will not retry. macOS App Nap can also throttle background processes even when the laptop is awake. The only reliable fix is a host that never sleeps.

How long does it take to set up an always-on host for Claude Cowork?

With Standby it takes about 10 minutes from purchase to first scheduled task firing: buy a plan, receive RDP credentials by email, connect from any device, open the pre-installed Claude Desktop, sign into your Anthropic account, then configure your tasks. DIY on a Windows VPS takes 1–2 hours of PowerShell setup plus ongoing Windows Update maintenance.

Claude Cowork scheduled tasks not firing? The 5 causes and the permanent fix

Updated June 1, 2026 · Standby Cloud LLC

TL;DR. 9 times out of 10, your Cowork scheduled task didn't fire because Claude Desktop wasn't running at that exact moment. Anthropic's own help docs confirm this: "scheduled tasks only run while your computer is awake and the Claude Desktop app is open." Sleep mode, closed lid, Windows update auto-reboot, app crash — any of these silently skip the task. The permanent fix is an always-on host that runs Claude Desktop 24/7.

What you searched for vs what's actually happening

You set up a Claude Cowork scheduled task — maybe a 6am daily briefing, a 4pm market summary, a sales-call prep at 9:50am. You went to bed (or to a meeting). The task time passed. Nothing happened. No notification. No error. Just… silence.

If that's familiar, you're in the right place. The behavior is by design and is documented by Anthropic, but very few users notice until a task they actually depended on silently fails.

The 5 causes, ranked by how often we see them

#	Cause	How to confirm	Fix
1	Computer was asleep, off, or Claude Desktop was closed at the scheduled time	Check your laptop's sleep history; check if Claude Desktop was open	Always-on host (jump to next section)
2	Claude Desktop was open but Cowork tab wasn't focused	Reproduce by setting a 5-min task with the Cowork tab on a different chat	Always-on host + auto-launch Claude in Cowork view
3	Windows Update or macOS update rebooted the machine	Check your OS update history around the scheduled time	Set update active hours wide; configure Claude to auto-launch on boot
4	Schedule syntax error (cron expression invalid, ambiguous timezone)	Open the task, check the "next fire" preview — if it shows "Never" or a wrong time, syntax is broken	Use the schedule UI rather than raw cron; verify the next-fire timestamp
5	Anthropic session token expired (every 30 days)	Open Claude Desktop, see if you're logged out	Re-sign in every 30 days; on a managed host this is the only manual maintenance step

The permanent fix: an always-on host

Causes 1, 2, and 3 — which together account for ~90% of the silent failures we see — all have the same fix: put Claude Desktop on a machine that never sleeps.

Three options, ranked by cost and reliability:

Option	Cost	Effort	Reliability
Leave your laptop running 24/7	Power: ~$8–15/mo electricity	Almost none, but you can't travel with it	Medium — laptops thermally throttle, OS updates still reboot
Mac mini or Windows mini-PC at home	$600+ one-time, plus power	~2 hours to set up	High when your home internet is up; vulnerable to outages
Managed cloud desktop (e.g. Standby)	$39/mo	~10 minutes	Highest — data-center power, redundant internet, automated maintenance

How Standby fixes this specifically: a dedicated Windows Server 2022 VM in a US data center, with Claude Desktop pre-installed, power-policy set to never sleep, Windows Update active hours suppressed, and Claude configured to auto-launch on boot with the Cowork tab focused. You sign into your own Anthropic account once. Scheduled tasks fire 365 days a year. Always-On Guarantee: if it's not running 24/7 within your first day, full refund. See pricing →

Step-by-step: verify your task will fire next time

Open Cowork → your task → confirm the schedule. The UI shows the next-fire timestamp. If it says "Never" or a date in the past, the syntax is broken.
Run a 5-minute test. Create a no-op task that fires 5 minutes from now (e.g. "Reply with 'OK'"). Walk away from the screen but leave the machine awake.
Check at 5 minutes. If it fired, the issue is host availability — your laptop sleeps or quits Claude when you're not looking.
Move to an always-on host. Either DIY (Mac mini / Windows mini-PC / VPS) or managed (Standby).
Re-test the 5-minute task from the new host. Now lock the screen, close your laptop, walk away. It should still fire.

What about Claude Code overnight runs?

Same root cause, same fix. We wrote a separate guide on overnight Claude Code runs — it's the same always-on-host problem from a different angle. If you're running long Claude Code refactors, the host that fixes one fixes the other.

What about Dispatch from your phone while you travel?

Same again. Dispatch needs Claude Desktop alive somewhere to receive your prompts. If you're a digital nomad, the cloud desktop solves all three problems with one $39/month subscription.

FAQ

Why didn't my 6am brief fire?

Almost certainly because your laptop slept overnight. Open your laptop's sleep history — you'll see it went to sleep before 6am. Sleep silently kills scheduled tasks. The fix is an always-on host.

Do scheduled tasks fire when Claude Desktop is minimized?

Minimized — yes, as long as the process is still alive. Closed (X'd out) — no. Backgrounded with the Cowork tab not focused — sometimes not, depending on the bug fix status. Safest pattern: always-on host with Claude Desktop launched into the Cowork view.

Will this fix work if my internet at home is flaky?

If you self-host (Mac mini / mini-PC), no — your home internet outage stops Claude from running. A cloud desktop fixes this because the data-center internet is redundant. Standby data centers run 99.9% uptime SLAs.

Is Linux an option?

No. Claude Cowork requires Claude Desktop (Windows or macOS only). Linux has the Anthropic API but no Cowork. More detail in our Linux server guide.

How is Standby different from running a Windows VPS myself?

You can absolutely DIY a Windows VPS (Contabo, Hostinger, Vultr — ~$13–16/month) and set it up over a couple of hours of PowerShell. Standby is the managed version — Claude Desktop pre-installed, configured, supported, and guaranteed. We wrote the full DIY guide here; pay for managed only if you'd rather not maintain Windows updates and PowerShell scripts yourself.

Try Standby — $39/month with Always-On Guarantee →

Founder runs support: hello@trystandby.com
All guides · trystandby.com