If Revit Cloud Worksharing is down, or you can’t access BIM 360 or Autodesk Construction Cloud (ACC), you’re likely dealing with a service-side issue—not your machine.
This has hit firms globally (Europe, US, Australia): models won’t open, sync fails, or login hangs. This guide breaks down what’s actually happening and how to protect your work while the system recovers.
What’s Happening: Global Revit Cloud Worksharing Outage
The recurring issue discussed on Autodesk forums is global service degradation affecting Revit Cloud Worksharing (RCW).
Typical symptoms:
- Revit cloud model cannot open
- Cannot access BIM 360 / ACC projects
- Revit stuck on loading or spinning wheel
- Sync to Central failing
- New cloud models cannot be created
In many cases:
- Existing sessions stay usable (partially)
- New sessions fail
- Authentication services become unstable
There is often a delay between the outage and the Autodesk Health Dashboard updating, which creates confusion. Note: many forum threads documenting these incidents date back to 2024–2025, but the behavior and mitigation strategies remain unchanged.
Why Revit Cloud Worksharing Fails
These outages are not random. They usually fall into a few categories:
1. Autodesk Server-Side Failure
- Core RCW services down
- Identity/authentication issues
- Cloud model database unavailable
2. Regional Service Instability
- EU, US, or APAC nodes affected differently
- Some users can connect, others cannot
3. Authentication Token Failure
- Login loops
- Cannot access cloud even if service is partially up
4. Local Cache Corruption (After Recovery)
- You still can’t connect after service is restored
- Caused by outdated session data
5. Infrastructure or Storage Issues
- Backend storage (Forge / AWS S3) instability
- Partial platform impact depending on region or service
6. Version or Compatibility Issues
- Mismatch between Revit version and cloud services
- Less common, but happens after updates
Quick Fix Checklist (Use This First)
If you’re under pressure, run this:
- Check Autodesk Health + forums
- If global → stop troubleshooting locally
- Do NOT close Revit
- Do NOT sign out
- Save a local backup (Save As Project)
- Wait before attempting sync again
Best Solutions and Professional Workarounds
When the cloud goes unstable, the goal is simple: don’t lose work and don’t make it worse.
1. Verify Real-Time Status
Do not rely only on the official dashboard.
Check:
- Autodesk Health page
- Forums
- Team reports across regions
If multiple regions report issues: → This is a server-side outage
Stop:
- reinstalling Revit
- resetting networks
- debugging your machine
It will not fix anything.
2. Do Not Close Your Active Session
If your model is open:
- Keep working locally
- Avoid closing Revit
Revit Cloud Worksharing handles intermittent connection better than a fresh login.
Closing the session during an outage can lock you out completely.
3. Save Locally (Last-Resort Safety Backup)
If Sync to Central fails, you can:
- Use Save As > Project
- Save to your local drive
This creates a recovery version of your work.
Critical limitation (often misunderstood):
- This breaks the link with the cloud central model
- This file cannot be synced back to the cloud
If you continue working on it for hours:
- You will need to manually re-integrate changes (copy/paste, reload families, etc.)
Use this only as: → a data protection measure, not a production workflow
4. The “Coffee Break” Rule
When the service is unstable:
- Stop syncing
- Stop forcing connections
- Wait
Forcing sync during degradation leads to:
- File in Use errors
- Element ownership conflicts
- Corrupted central models
Sometimes the correct move is to step away.
Advanced Troubleshooting (After Service Recovery)
Once Autodesk confirms services are back:
Clear Web Services Cache (Targeted Method)
Path:
%localappdata%\Autodesk\Web Services
Recommended approach:
- Close Revit
- Delete LoginState.xml only
This forces:
- credential refresh
- new authentication handshake
Important:
- Deleting the entire folder will log you out of all Autodesk services
- Use full deletion only if the targeted fix fails
Review Revit Journal Files
Path:
%localappdata%\Autodesk\Revit\Autodesk Revit 20XX\Journals
Look for:
- CloudResourceManagerException
- connection errors
This confirms: → issue was external, not your machine
Common Error Messages and What They Mean
These are typical during outages:
- “Cannot open cloud model” → service unavailable
- “Revit Cloud Model not accessible” → authentication failure
- “Communication with server failed” → backend service down
- “Sync to Central failed” → RCW instability
If multiple users see the same error: → stop troubleshooting locally
BIM 360 vs Autodesk Construction Cloud (ACC): Are Both Affected?
In most cases, yes.
Both platforms rely on:
- Revit Cloud Worksharing (RCW)
- shared identity services
However, in real incidents:
- Authentication outages can block access globally
- Regional infrastructure issues can affect only EU or US environments
- Storage/backend failures can impact one platform or region more than another
So while they usually fail together, partial outages do happen.
FAQ: Troubleshooting Revit Cloud Access
Why does the Autodesk Health Dashboard show “Operational” when I can’t log in?
The dashboard is updated after confirmation from Autodesk teams. There is typically a 30–60 minute delay between the start of an outage and the status update.
Is BIM 360 down today?
If:
- multiple users across regions report issues
- Revit cloud models won’t open
- login or sync fails
Then yes, it’s likely a live service outage, even if the dashboard still shows green.
Why can’t I open my Revit cloud model?
Most common causes:
- RCW service down
- authentication failure
- regional outage
If others report the same issue: → it’s not your file or machine
Can I work offline on a Cloud Workshared model?
No, not in the standard sense.
Revit Cloud Worksharing requires server communication to:
- borrow elements
- sync changes
However, there is one exception:
If you previously:
- checked out (extracted) entire Worksets
Then you can:
- continue working on those Worksets locally
You still cannot:
- sync changes
- borrow new elements
This is the closest thing to a degraded offline workflow.
Will I lose my work if the cloud crashes while syncing?
Usually:
- Revit rolls back the transaction
Still:
- keep the session open
- avoid repeated sync attempts
- create a local backup when possible
Does this affect both BIM 360 and Autodesk Construction Cloud (ACC)?
Most of the time, yes.
But depending on the failure:
- authentication
- region
- storage layer
It is possible for one environment to behave differently from another.
What is the first thing a BIM Manager should do during an outage?
Send a firm-wide message:
- Do NOT close Revit
- Do NOT sign out
- Do NOT force sync
Signing out during an identity service outage can prevent users from logging back in when services recover.
Field Notes from BIM Leads
From real incidents:
- Teams that kept sessions open avoided data loss
- Teams that forced sync created conflicts
- Teams that waited recovered cleanly
This is not a software problem you fix locally. It’s a coordination problem during a cloud failure.
Bottom Line
When Revit Cloud Worksharing is down, the priority is:
- protect your local work
- avoid breaking the central model
- wait for service stability
If it’s global, no local fix will solve it.
Act accordingly.