Fix Broken AI Automations (Claude AI Troubleshooting Guide)

If you want to fix broken AI automations without spending hours guessing, you need a repeatable troubleshooting order — basics, permissions, prompt — and that's exactly the framework I use across every Claude Desktop setup I run.

Direct Answer: To fix broken AI automations in Claude, work through three checks in this exact order: confirm the basics (computer awake, Claude Desktop open, internet on), then verify permissions (connector tokens, folder access, admin restrictions), and finally refine the prompt for clarity and context. Roughly 90% of failures resolve at the basics or permissions layer before you ever touch the prompt.

Here is something nobody tells you when you first start automating with Claude: things will break. Not because the tool is flawed, not because you did something wrong, but because automations depend on a chain of conditions all lining up at the right time — and sooner or later one link in that chain slips. As someone who has trained 79,000+ students across 74+ courses on AI and automation from Dubai, I've watched the same six issues repeat across thousands of setups. Below are the fixes.

Problem 1: Your Scheduled Task Didn't Run

This is the number one issue I see, and it has the simplest explanation. Scheduled tasks only run when two conditions are both met: your computer is awake, and Claude Desktop is open. If your laptop went to sleep at 2:00 a.m. and your task was scheduled for 3:00 a.m., it simply did not execute — there is no cloud server running it in the background.

The fix is straightforward. On Mac, adjust your sleep settings inside System Preferences. On Windows, check your power and sleep settings. Then verify whether the task actually ran: open Claude Desktop, go to the Scheduled Tasks page, and look at past runs. The log shows exactly when each task last executed and where the gaps are. I recently spotted a 16th and 17th April gap on my own daily enrichment task this way — that log is always your first stop.

Problem 2: Connector Authentication Expired

You set up a connector to Google or Notion. It worked great for two weeks, and now Claude says it can't access the integration. What happened? OAuth tokens expire. This is standard behaviour across almost every connected service — not a Claude-specific issue.

The fix takes 60 seconds. Go to Settings, then Connectors, find the integration that stopped working, disconnect it, and reconnect. You'll go through the authentication flow again and you're back in business. Build a habit of re-authenticating any connector you haven't touched in 14+ days before depending on it for a critical run.

Problem 3: Dispatch Is Not Connecting

You're trying to send a task from your phone using Dispatch, but nothing is happening on the desktop side. Two things to check immediately: both devices need to be signed in to the same Claude account, and the desktop app needs to be running on an awake computer. If the desktop is asleep or the app is closed, Dispatch has nowhere to send the task.

Verify both devices are on the same account, then check internet connectivity on both ends — Dispatch needs a live connection on phone and desktop simultaneously. This is the same root cause as Problem 1, just dressed differently: an asleep desktop kills both scheduled tasks and Dispatch hand-offs.

Problem 4: Task Produces Wrong or Unexpected Output

Your task ran, but the result isn't what you wanted. Maybe the summary is too short, it pulled the wrong data, or it missed the point entirely. Nine times out of ten, this is a prompt problem, not a tool problem.

Edit your scheduled task prompt to be more specific. Add context. Tell Claude exactly what format you want, what to include, and what to ignore. If the task reads files, make sure you've granted folder access so Claude has the source material it needs. Treat your prompt like a draft — review the output, refine, repeat. As a Chartered Accountant, my instinct is to be precise about inputs and outputs, and that same precision is what turns a flaky scheduled task into a reliable one.

Problem 5: Connector Permissions Are Insufficient

Claude is connected to your tool, but it can't access certain files or perform certain actions. This usually means one of two things: either your permissions in the source system are limited, or your organisation's Team or Enterprise admin has restricted what connectors can do.

First, check your own permission in the source system — can you access that file or folder directly? If not, that's the issue, and Claude inherits your access level. If you can access it but Claude can't, then check with your admin about organisation-level connector restrictions. Some organisations deliberately limit what Claude can read or write for security reasons, and no amount of prompt tweaking will override that policy.

Problem 6: Task Ran but Files Don't Appear

Your task executed successfully according to the logs, but you can't find the output files anywhere. This almost always means one thing: you didn't grant folder access for that specific scheduled task.

Open the scheduled task and make sure a folder designation is set. Without it, Claude has no location to save files to. Assign the correct folder, run the task again, and your files will appear right where you expect them. Folder access is per-task, not global — so even if one task can write to a folder, another task on the same machine still needs its own permission grant.

The Three-Step Troubleshooting Framework

Memorise this order — it resolves almost everything without outside help:

• Step 1 — Check the basics: Is the app open? Is the computer awake? Is there an internet connection? This alone solves the majority of issues.
• Step 2 — Check permissions: Are connectors authenticated? Does the source system allow access? Are there admin restrictions? Is folder access granted on the task?
• Step 3 — Check the prompt: Is it specific enough? Does it have the context it needs? Does the task have what it needs to read and write?

Work through these three steps in that order. Once you internalise this sequence, you stop feeling stuck when something breaks and start feeling like the person who just solves problems fast — which, honestly, is the entire point of building automations in the first place.

Six problems, six fixes, one framework — that is how you fix broken AI automations in Claude without losing a workday to guesswork. Your next step today: open Claude Desktop, go to your Scheduled Tasks page, and audit the last 7 days of runs for any gaps before you trust the next one to fire.