Autodesk experienced a minor incident on June 22, 2026 affecting Forma Build and Forma Build (European Union), lasting 37m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 22, 2026, 06:46 PM UTC
We are investigating reports of customers experiencing an issue where they are unable to access the Submittals module within Forma Build. We are actively looking into this and we will provide an update within 60 minutes or sooner if we have more information to share.
- investigating Jun 22, 2026, 07:18 PM UTC
We are continuing to investigate reports of customers experiencing an issue where they are unable to access the Submittals module within Forma Build in the US region. We subsequently determined that the cause of this issue was also affecting Forma Build in the European Union. 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 22, 2026, 07:23 PM UTC
The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.
- postmortem Jul 14, 2026, 12:59 PM UTC
**AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc146883-acssbmfe-p **Incident Date:** June 22, 2026 **Summary** On June 22, 2026, between 09:30 AM PDT and 12:20 PM PDT Autodesk Forma Build Submittals in the US region experienced a service disruption after a production deployment. The issue mainly affected the Submittals item list workflows. Some requests timed out before the backend application could begin processing them, causing users to see failed or delayed page/API loads. **Impacted Services** * Forma Build Submittals. **Root Cause** * The incident was triggered by a production deployment The deployment introduced comments/mentions improvements that increased database activity in high-traffic Submittals APIs. The issue was resolved by manually rolling back the US region production deployment. **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Fixing the root cause issue related to the comments DB improvement. The team fixed the specific place in code that caused the increase of item list API processing time including tests. * Fixing BIM360WF 504 alerting — validate alert configuration across regions/environments and setup DT 504 alert definitions from account scope to service. * Add a skill that after deployment it detects abnormal behavior of the service. * Establish stress and load testing for high-traffic APIs across QA, STG, and PROD. Thank you for your patience and understanding.