Autodesk experienced a minor incident on July 30, 2026 affecting Revit Cloud Worksharing / Cloud Models, lasting 42m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 30, 2026, 05:07 AM UTC
We are investigating an issue where customers are experiencing issues with initial collaboration and synchronous central synchronization in Revit Cloud Worksharing / Cloud Models in the US region. We are actively looking into this and we will provide an update within 60 minutes or sooner if we have more information to share.
- resolved Jul 30, 2026, 05:49 AM UTC
The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.
- postmortem Sep 04, 2026, 02:06 PM UTC
**AUTODESK EVENT ANALYSIS** **Incident Number:** #COE-INC151602, #COE-INC151694 **Incident Date:** July 29, 2026, July 30, 2026 **Summary** On July 29, 2026, from 9:30 PM to 10:40 PM PDT and on July 30, 2026, from 11:12 PM to 11:45 PM PDT, Autodesk customers using Revit Cloud Worksharing / Cloud Models in the US region experienced issues accessing cloud model workflows, including Initiate Collaboration, Synchronize with Central, and Model Open. **Impacted Services** • Revit Cloud Worksharing / Cloud Models in the US region **Root Cause** • A routine database maintenance procedure triggered an expected failover event. • Though past events have not disrupted customer workflows, this one unexpectedly resulted in a reduction in service capacity, degrading its ability to handle customer requests. • As the service began to recover, customer demand exceeded available capacity, delaying a return to normal operation. • Autodesk temporarily limited demand and gradually lifted the limit as capacity recovered, restoring the service to normal operation. **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken, including: • Update maintenance procedures to reduce the risk of disruption. • Improve service resilience to better tolerate brief disruptions to supporting systems. • Process improvements to operational response when demand exceeds capacity during recovery. Thank you for your patience and understanding.