Autodesk incident
Forma Build | Forma Data Management | Forma Takeoff
Autodesk experienced a minor incident on July 29, 2026 affecting Forma Build (Australia) and Forma Data Management (Australia) and 1 more component, lasting 55m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 29, 2026, 02:09 PM UTC
We are investigating an issue where customers are unable to create and access new projects in Forma Build, Forma Data Management and Forma Takeoff in the Australia 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 29, 2026, 03:04 PM UTC
The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.
- postmortem Aug 29, 2026, 05:35 PM UTC
**AUTODESK EVENT ANALYSIS** **Incident Number:** COE-INC151562 **Incident Date:** July 29, 2026 **Summary** From July 28, 2026, at 9:44 AM PDT to July 29, 2026, at 7:53 AM PDT, Autodesk Forma experienced an issue that prevented customers from creating and accessing new projects in the Australia \(AUS\) region. The incident impacted customers using Forma Build, Forma Data Management, and Forma Takeoff. Existing projects remained available and continued to function normally throughout the incident. **Impacted Services** * Forma Build * Forma Data Management * Forma Takeoff **Root Cause** * A recent infrastructure deployment recreated a messaging component with an incorrect configuration, preventing project initialization events from being processed for newly created projects in the Australia region. **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Corrected the messaging configuration, restoring normal processing of project initialization events. Autodesk also initiated recovery of the projects affected during the incident. * Strengthen deployment validation to verify that messaging components are created and configured correctly before infrastructure changes are promoted to production. * Improve end-to-end monitoring of project initialization workflows, so messaging failures are detected more quickly. Thank you for your patience and understanding.