Cowork Troubleshooting: 6 Most Common Issues and Fixes (2026)

Cowork Troubleshooting: 6 Most Common Issues and Fixes (2026)

A well-configured Cowork setup delivers the seamless experience it was designed for: your desktop reads the right folder, talks cleanly to connectors, produces artifacts, and posts digests exactly where your team lives. Most teams see these six issues surface during the first few weeks. Each has a known fix, and once you've walked through them, the tool runs quietly in the background.

This is the troubleshooting checklist we walk new Cowork users through. All six issues, all six fixes, in the order they typically appear.

RPC Failed When Calling a Connector

You see a red banner that reads RPC failed or connector tool returned an error mid-chat. Cowork tried to reach one of your installed connectors (Slack, Gmail, Drive, Calendar, etc.) and the call was rejected before any work happened. The fix is almost always a 30-second token refresh or a connector reinstall. See the full troubleshooting guide for the exact steps.

→ Read: "Cowork: 'RPC Failed' Error When Calling a Connector — Fix"

JSON Parsing Failure Mid-Response

How ScaleIT handles this: See AI Quick-Start

A chat reply stops mid-sentence with a parse error, usually when Cowork is converting connector data into a structured artifact (table, tracker, spreadsheet). The connector returned data that Cowork expected to be JSON, and one field broke the parse. The fix is often a simple retry or a tighter request scope. Full details below.

→ Read: "Cowork: JSON Parsing Failure Mid-Response — Fix"

The App Freezes or Stops Responding

A Cowork window stops accepting input, leaves a spinner running, or appears to hang for a minute or longer. The chat usually still works underneath; it's the UI thread that has stalled. You'll get the app back in about 30 seconds with a reload or a cancel button click. Step-by-step escalation here.

→ Read: "Cowork: App Freezes or Stops Responding — Fix"

Mobile App Missing Desktop Features

You're trying to use Cowork on iPhone or Android and finding that file tools, scheduled tasks, plugins, and local connectors aren't available like they are on the desktop. This is by design, not a bug. Mobile is optimized for reading; desktop handles the heavy lifting. Here's how to design workflows that work across both.

→ Read: "Cowork: Mobile App Missing Desktop Features — What to Do"

Folder Access Not Picking Up the Right Files

You ask Cowork about files in a folder and get back a response that ignores them, says the folder is empty, or names files that aren't there. The issue is usually either no folder is selected or the wrong folder is selected. One click in the folder picker fixes it; full diagnostics here.

→ Read: "Cowork: Folder Access Not Picking Up the Right Files — Fix"

Scheduled Tasks Not Firing

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 a sleeping desktop, an expired connector token, or a confirmation dialog waiting for approval. All three have quick fixes.

→ Read: "Cowork: Scheduled Tasks Not Firing — Fix"

Set Your Team Up for a Smooth Month Ahead

Most of these issues never surface on a properly configured install. The first-week setup that pays off for months includes:

If your team started with defaults and has already worked around two or three of these, you're on the normal path. A focused troubleshooting session gets the install into smooth operation for the quarter ahead.

Looking to deploy Cowork across your team without weeks of setup and troubleshooting? ScaleIt can help. Contact us for a free consultation to get your instance running smoothly.