Cowork: Scheduled Tasks Not Firing — Fix

A daily or weekly task that ran cleanly during setup goes silent. The Slack post doesn't arrive, the report doesn't generate, the tracker doesn't update. The three most common causes are your desktop was asleep at task time, a connector token expired, or a confirmation dialog is waiting for human approval. All three have quick fixes.

Quick Fix: Check Desktop Status & Connector Auth

1. Verify your desktop or laptop was on and unlocked at the task's scheduled time. Scheduled tasks only run when the Cowork process is alive.
2. Open Cowork and go to Customize → Connectors. Look for any connectors with a warning icon or stale auth.
3. If a connector looks expired, click it and re-authenticate. Then manually trigger the task by clicking Run Now or re-running the task prompt.
4. If the manual run succeeds, your connectors are healthy and the issue was likely a sleeping machine.

If manual run fails, see "Still Broken?" below.

Desktop Was Asleep (Most Common)

How ScaleIT handles this: See AI Quick-Start

Scheduled tasks run when the Cowork desktop process is alive. A laptop closed at 9 a.m. cannot fire a 9 a.m. job. A machine in sleep mode will not run the task until it wakes.

Fix: You have two options:

1. Keep the machine on during the task window. For a critical 9 a.m. report, ensure your machine is awake and unlocked at 9 a.m. Set a calendar reminder to keep an eye on the machine.
2. Shift the schedule to a reliable time. If your machine is always on at 4 p.m. but sometimes asleep at 9 a.m., reschedule the task to 4 p.m. Open the task in Cowork, click Edit, update the schedule (usually a cron expression like 0 16 * for 4 p.m.), and save.

For teams with laptop-based setups, scheduling tasks for afternoon hours (when people are usually at their desks) is more reliable than early morning.

Expired Connector Token (Second Most Common)

The task itself is healthy, but a Slack or Gmail token expired between runs. The next scheduled run tries to use the expired token and silently fails (or pauses waiting for re-auth).

Fix:

1. Open Cowork and go to Customize → Connectors.
2. Click each connector the task depends on (usually Slack, Gmail, Drive, or Calendar).
3. If you see a prompt to re-authenticate, click it and walk through the OAuth flow.
4. The task should complete cleanly on its next scheduled run, or you can click Run Now to test immediately.

For high-stakes recurring tasks (daily client reports, weekly board updates), set a calendar reminder to re-authorize connectors monthly. OAuth tokens vary by vendor, but monthly re-auth prevents most surprises.

Task Paused for Confirmation Dialog

Tasks that perform write actions (sending a Slack message, creating a file in a shared drive, or posting to a calendar) sometimes pause and wait for human confirmation depending on your Cowork settings. The task doesn't fail; it's waiting in the background for approval.

Fix:

1. Open Cowork and navigate to Tasks or Scheduled Tasks (exact label varies by Cowork version).
2. Find the paused task in the task history.
3. Click it to view the confirmation dialog.
4. Review the proposed action and click Approve to let it complete, or Revise to modify the action before it runs.
5. After approval, the task resumes and completes.

If you want tasks to run without prompts, adjust your Cowork security settings. Go to Settings → Security and lower the confirmation level for write actions, or disable the confirmation for trusted connectors like your own Slack workspace.

Verify

• A manual run of the task completes without errors (click Run Now or re-run the prompt).
• If the task posts to Slack or email, the message arrives.
• Check the task history or logs. Most scheduled tasks show a timestamp of the last successful run.

Still Broken?

If all three checks above are complete and the task still doesn't fire on schedule:

1. Note the exact task name and schedule. Example: "Morning Report, 8:00 AM UTC daily."
2. Check the task's most recent run in the history. Look for error messages or failure timestamps.
3. Ensure your machine is on and unlocked at the scheduled time. Run a manual test: stay at your desk at the exact scheduled time and watch Cowork. Does the task fire?
4. Verify connector status. Re-authenticate any connector the task uses, even if it looks healthy.
5. Contact ScaleIt with the task name, schedule, the most recent error (if any), and the steps you've taken. We can investigate whether the task scheduler is misconfigured or whether there's an issue with a specific connector.

Missing critical task runs because of configuration issues? ScaleIt helps teams design and implement reliable scheduled workflows. Contact us for a free consultation.