Last Tuesday I had three people ping me within an hour saying their WorkDrive folders hadn't synced since the previous evening. No error. No notification. The little tray icon just sitting there looking perfectly fine. That's somehow more infuriating than a red error message, because at least a red message tells you something's wrong.

I've managed Zoho Workplace for about 80 users across two office locations and a handful of remote folks. WorkDrive sync going quiet is one of those issues that comes up way more than it should. And the worst part? The official Zoho support docs are... not great. They'll tell you to reinstall the sync agent like that's a complete answer. Sometimes it is. Usually it's not.

So here's what I've actually learned from digging into this repeatedly, so you don't have to spend four hours on it like I did the first time.

Table of Contents

• What's Actually Happening When WorkDrive Sync Stops
• Fix 1: Restart and Reinstall the WorkDrive Sync Agent
• Fix 2: Check Folder Permissions and Sync Scope Settings
• Fix 3: Clear the Sync Cache and Force a Re-index
• Fix 4: Firewall, Antivirus, and Proxy Conflicts
• Common Mistakes People Make

What's Actually Happening When WorkDrive Sync Stops

The WorkDrive desktop sync client is a separate application from the browser version. It runs as a background agent on Windows or Mac and is responsible for keeping your local folder in sync with the cloud. When it breaks, it usually breaks silently.

The most common causes I've seen are the sync agent crashing or freezing without killing its process, a file or folder name conflict (special characters, path too long, that kind of thing), the local sync cache getting corrupted, or something on the network side — proxy settings, firewall rules, or antivirus software blocking WorkDrive's sync traffic.

Here's the thing that trips people up: WorkDrive will sometimes show "Synced" in the tray even when it hasn't synced in hours. The status display isn't always reliable. So the first thing to establish is whether sync has genuinely stopped by checking the actual file timestamps in your local folder versus what you see in the web version of WorkDrive. If they differ, sync is broken regardless of what the tray icon says.

Fix 1: Restart and Reinstall the WorkDrive Sync Agent

Start here. Always. It solves maybe 40% of cases.

On Windows, right-click the WorkDrive icon in the system tray and click Quit WorkDrive. Then open Task Manager and make sure there's no ZohoWorkDrive.exe process still running. If there is, kill it. Then relaunch WorkDrive from the Start menu.

On Mac, click the WorkDrive menu bar icon, choose Quit, then check Activity Monitor for any lingering WorkDrive processes and force quit them.

If a restart doesn't fix it, do a clean reinstall. Uninstall WorkDrive completely from your system, then grab the latest installer from workdrive.zoho.com — go to the bottom left of the interface and look for the desktop app download link. Don't use an old installer you have sitting around. The agent updates somewhat frequently and older versions have had sync bugs that were fixed in newer releases.

After reinstalling, sign in fresh and let it do the initial sync. Give it 10-15 minutes before you panic.

Fix 2: Check Folder Permissions and Sync Scope Settings

This one catches people off guard. WorkDrive has granular sharing permissions that affect what the desktop client can and can't sync.

If you're syncing a Team Folder, go to workdrive.zoho.com, open the Team Folder in question, and check your role. If your role was recently changed from Manager to Member, or if someone adjusted the folder's external sharing settings, the sync client might have silently lost access to certain subfolders.

Also check your sync scope settings in the desktop app itself. Click the WorkDrive tray icon, go to Preferences, then Sync Settings. You'll see which Team Folders and sub-folders are actually selected for sync. I've had cases where a user was convinced everything was syncing but they'd accidentally unchecked a folder in here months ago and never noticed.

On Windows, also make sure the local WorkDrive sync folder isn't inside a OneDrive or Google Drive managed folder. Nested sync clients fighting over the same directory is a mess and WorkDrive will usually lose quietly.

Fix 3: Clear the Sync Cache and Force a Re-index

The sync cache is where WorkDrive stores its local record of what's been synced. If this gets corrupted — which can happen after a crash, a hard shutdown, or sometimes just randomly — sync breaks and the client has no idea why.

On Windows, the cache lives here:

Quit WorkDrive completely first. Then go into that folder and delete the sync_cache subfolder. Don't delete the whole ZohoWorkDrive directory, just the cache folder. Then restart WorkDrive. It'll re-index everything from scratch, which takes a few minutes, but this has fixed sync for me when nothing else worked.

On Mac, look in:

Same deal — find and delete the cache folder, then relaunch.

One warning: if you have files that exist only locally and haven't uploaded yet, back those up somewhere else before you do this. Rare situation but worth mentioning.

Fix 4: Firewall, Antivirus, and Proxy Conflicts

This is the one corporate IT folks run into more than home users. WorkDrive sync uses specific endpoints to communicate with Zoho's servers. If your firewall or proxy is blocking those, sync breaks completely.

WorkDrive needs access to *.zoho.com, *.zohostatic.com, and *.zohoapis.com on ports 443 and 80. If you're running a strict outbound firewall, check whether those are whitelisted.

Antivirus is sneakier. Tools like Symantec or even Windows Defender can sometimes quarantine WorkDrive's sync process or block it from writing to the local folder. Check your AV logs and add ZohoWorkDrive.exe as an exception if needed.

Proxy settings are the worst to debug. If your network uses a proxy, open WorkDrive Preferences, go to Network, and set the proxy configuration manually to match your system proxy. The "Use System Proxy" option doesn't always work reliably, honestly.

Common Mistakes People Make

Skipping the cache clear and jumping straight to reinstalling. Sometimes reinstalling alone won't fix a corrupted cache because the reinstall doesn't always wipe it.

Not checking the web version first. If the files aren't showing in the web version of WorkDrive either, the problem is on the upload side, not sync. That's a different issue entirely.

Running multiple user accounts through the same WorkDrive client. WorkDrive desktop currently works with one account at a time per installation. Trying to switch between accounts without properly signing out causes weird partial-sync states.

Assuming sync failures are always client-side. Occasionally Zoho has backend issues that affect sync. Check status.zoho.com before you spend an hour troubleshooting locally. I've been burned by this more than once.

Ignoring long file paths on Windows. If a file path inside your WorkDrive folder exceeds 260 characters, Windows will silently refuse to create it and sync will stall. Enable long path support in Windows 10/11 via Group Policy or just keep your folder nesting shallow.

Hope this saves you the better part of an afternoon. WorkDrive is genuinely useful once sync is stable, but getting to that stable state can take some patience. If you've tried everything here and it's still broken, reach out to Zoho support with the sync logs — you can export them from Preferences inside the desktop app. They're actually helpful once you get past the first-level responses.