Autodesk experienced a minor incident on June 23, 2026 affecting Revit Cloud Worksharing / Cloud Models, lasting 1h 6m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 23, 2026, 04:46 AM UTC
We are investigating an issue where customers are unable to publish their workflows 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 Jun 23, 2026, 05:52 AM UTC
The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.
- postmortem Jun 29, 2026, 01:44 PM UTC
**AUTODESK EVENT ANALYSIS** **Incident Number:** #COE-INC146927 **Incident Date:** June 22, 2026 **Summary** On June 22, 2026, between 9:00 PM PDT and 10:00 PM PDT, Autodesk customers in the US region were unable to publish Revit Cloud Models to Forma Data Management. **Impacted Services** * Revit Cloud Models in the US region **Root Cause** * The service that supports publishing Revit Cloud Models became overloaded and stopped responding. * This was due to a recent service change which introduced additional processing time during publish requests. * The issue was more noticeable during bursts of publishing activity in the US region. * As a result, customers in the US region were temporarily unable to publish Revit Cloud Models to Forma Data Management. * We restored service by disabling the feature flag, which allowed the service to recover and return to normal operation. **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Increasing available service capacity and reviewing scaling settings so services can better handle sudden increases in publishing activity. * Updating the service to process publish requests more efficiently and avoid conditions that can cause requests to build up. * Improvements to how the service handles slower downstream responses. Thank you for your patience and understanding.