An Error Occurred While Communicating With The Cloud Worksharing Service | Fix Checklist

Seeing “an error occurred while communicating with the cloud worksharing service” can feel like the model just slammed the door. One minute you’re opening a cloud model or syncing, the next you’re stuck. The good news is that this message is rarely random. It tends to show up when Revit can’t reach the cloud service, can’t prove who you are, or hits a problem inside the model package.

This guide walks you through a direct path: start with the quick wins, then move into network and account checks, then finish with model health steps. If you work in a managed IT setting, you can hand the network section to your IT teammate and keep moving.

What This Cloud Worksharing Message Is Telling You

That error text is a generic “communication failed” banner. It does not point to one single cause. Revit cloud worksharing depends on several pieces working at once: your Autodesk sign-in token, your project access in Autodesk Construction Cloud, your local cache, and stable HTTPS traffic to Autodesk services.

When any link in that chain breaks, Revit may still show your project list but fail at the moment it needs to open, reload, or sync the model. Autodesk’s own Revit help and technical articles describe this message in cloud worksharing and tie it to both connectivity problems and model or link corruption cases.

What You See	Likely Cause	First Move
Error appears before the model loads	Service outage, blocked network, or sign-in token issue	Check Autodesk Health Dashboard, then sign out and in
Error appears while syncing	Network drop, proxy inspection, or cache conflict	Try a different network, then clear the local cache
Error only on one project/model	Corrupt link, bad workset state, or damaged model element	Open with worksets closed, then unload links and test

Quick Checks That Fix Most Cases In Minutes

Start here. These steps solve a large share of cases because they target the three most common triggers: a temporary service issue, a stale sign-in token, or a broken local cache.

• Check Autodesk Health Dashboard — If Revit Cloud Worksharing or Cloud Models show an incident, wait for service restore before chasing local fixes.
• Close Revit, then reboot — A reboot resets pending network hooks and clears stuck sign-in processes.
• Sign out, then sign back in — In Revit, sign out of your Autodesk account, close Revit, reopen, and sign in again to refresh your token.
• Try a different network — Use a mobile hotspot or home network to rule out office firewall, proxy, or SSL inspection.
• Update Revit — Install the latest Revit update for your version, since cloud features rely on current components.

If your firm uses single sign-on, try signing in through a browser first, then reopen Revit. If that works, your desktop token was stale and now refreshed for this session today.

If the model opens after these checks, do a quick sync right away. If it syncs once, you’ve confirmed the link is back and you can return to normal work.

Network And Security Blocks That Stop Cloud Worksharing

Cloud worksharing traffic is normal HTTPS, but many corporate networks still break it. Proxy servers, SSL inspection, and strict outbound filtering can block the domains Revit needs. Autodesk posts notes on proxy settings and domain exceptions for Collaboration for Revit and related services.

Proxy And Firewall Checks

If you’re behind a proxy, the proxy may require exceptions for Autodesk cloud endpoints. Some setups allow a browser to sign in while Revit fails because the desktop app traffic is treated differently. Start by testing the same sign-in and model open process on an unrestricted network. If that works, the issue sits in the office network path.

• Confirm proxy rules — Ask IT whether a proxy is in use and whether Revit is allowed to pass through it without authentication popups.
• Add domain exceptions — Add Autodesk cloud domains to the allow list so traffic is not blocked or re-written by inspection tools.
• Allow required ports — Ensure outbound HTTPS traffic is permitted to Autodesk services from the workstation.
• Test SSL inspection — Temporarily disable SSL inspection for Autodesk domains to see if the error disappears.

TLS And Windows Updates

On older Windows builds or older patch levels, missing TLS updates can cause cloud calls to fail. Autodesk lists Revit errors tied to missing TLS updates, including cases where cloud model services can’t be reached. If you see the error only on one older machine, this is a strong lead.

• Run Windows Update — Install pending security updates, then reboot before testing Revit again.
• Update Internet components — Keep system web components current since Revit relies on them for secure connections.
• Check system time — Fix incorrect date or time, since TLS validation can fail when the clock is off.

Account, Licensing, And Access Problems That Look Like A Network Error

Sometimes the network is fine and the account path is the real blocker. If Revit can’t confirm your identity or your project rights, the app can still surface a communication error. The clue is that other users can open the same model, or you can open other projects but not this one.

Sign-In Token And Identity Refresh

Tokens can expire, cached credentials can corrupt, or the desktop sign-in component can fall out of sync after password changes. A clean sign-in cycle fixes a lot of these.

• Sign out fully — Sign out in Revit and also in Autodesk Desktop App, then restart Windows.
• Remove saved credentials — Clear stored Autodesk sign-in data, then sign in again with fresh credentials.
• Check multi-factor prompts — Complete any MFA prompts in the browser if your org uses MFA, then retry in Revit.

Project Rights And Folder Access

Autodesk Construction Cloud permissions are granular. You might have project access but not the specific folder or model. If the error appears for one model only, confirm your role and rights in the project, and check whether the model was moved or replaced.

• Verify project membership — Confirm you’re still a member of the ACC project and not removed from the team.
• Confirm model location — Open the project in the web portal and confirm the model exists where Revit expects it.
• Check region and hub — Make sure you’re opening the model from the correct hub, since a wrong hub can look like missing access.

An Error Occurred While Communicating With The Cloud Worksharing Service In One Model

When the message only hits one file, shift from connectivity toward model health. Autodesk’s Revit help notes that corruption in a host model or a linked model can trigger the communication error. Autodesk technical notes for BIM-hosted models also point to testing with worksets closed and unloading links to isolate the bad piece.

Open The Model In A Safe State

The goal is to open the host with the least amount of linked content. That reduces the chance that a broken link or heavy workset crashes the open process before you can act.

• Open with worksets closed — In the Open dialog, close all worksets, then open the model and see if it loads.
• Unload links — If it opens, unload Revit links using the “Unload for me” option, then sync and test.
• Reload worksets one at a time — Open main worksets in small batches to find the one that triggers the failure.

Audit And Clean The File

If you can open the model after stripping links, take the chance to clean it. Auditing and compacting can reduce corruption risk. If the model is large, do this from a stable wired connection and avoid running heavy add-ins during the test.

• Run an audit open — Use Revit’s Audit option when opening to catch and repair common file issues.
• Compact the model — Compacting reduces file bloat and can help after many sync cycles.
• Check linked files — Open each linked model on its own and repeat the workset and audit checks.

Local Cache, Desktop Connector, And Sync Hygiene

Revit cloud worksharing uses a local cache for performance. If that cache gets out of alignment with the cloud copy, the app can misbehave in strange ways. Clearing cache is not glamorous, but it’s one of the most reliable fixes when the error appears after a crash or after switching networks.

Clear The Collaboration Cache

Close Revit first. Then clear the collaboration cache folders for your Revit version so a fresh cache can rebuild on the next open. After you clear it, open the model again and let the first load finish without interrupting it.

• Close Revit fully — Confirm Revit is not running in Task Manager.
• Remove cache folders — Delete the CollaborationCache and PacCache folders tied to your user profile for that Revit version.
• Open once and wait — The first open can take longer while the cache rebuilds, so let it finish.

Desktop Connector Checks

If you use Desktop Connector for related cloud docs, a stale project selection can cause linked workflows to fail. Autodesk troubleshooting for cloud model link cases includes reselecting the project in Desktop Connector when certain cloud opens fail.

• Restart Desktop Connector — Quit it fully, then reopen and let it finish syncing.
• Re-select the project — Disconnect and reconnect the project in Desktop Connector so the local mapping resets.
• Pause large sync jobs — Temporarily pause big folder syncs while you test Revit open and sync.

Preventing Repeat Errors On Busy Teams

Once you’re back in, it’s worth setting a few habits that cut repeat errors. Cloud worksharing is steady when the model stays clean, links stay sane, and the team syncs with a bit of discipline. Autodesk also publishes best practice notes to improve cloud workshared model performance.

• Keep Revit current — Apply updates across the team so all users run the same cloud components.
• Stabilize your network — Favor wired connections for big sync sessions and avoid switching networks mid-session.
• Limit heavy links — Break large linked models into manageable pieces and keep unused links unloaded.
• Sync with care — Sync before long breaks and at the end of sessions to reduce big merge events.
• Watch outage notices — Subscribe to Autodesk health alerts so you know when a cloud event is the real cause.

If you still see “an error occurred while communicating with the cloud worksharing service” after all of the steps above, capture the exact moment it happens: opening, reloading latest, or syncing. Note whether it happens on all networks or only one. That short note makes the next round of troubleshooting faster, whether you run it yourself or hand it to IT.