Autodesk Outage History

**AUTODESK EVENT ANALYSIS** **Incident Date:** April 28, 2026 **Summary** On April 28, 2026, between 6:20 AM PDT and 7:33 AM PDT, Autodesk customers were unable to view thumbnails for newly created design data across Fusion, Fusion Online, Fusion Mobile, and Fusion Team in all regions. **Root Cause** * Thumbnail creation was delayed due to queuing issues which in turn led to thumbnail failures * We added more workers/solvers that could free up the queue quicker which resolved the problem ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * We have identified the root cause of what led to the back-up, and are working to correct the problem * Additional monitoring alerts for detecting similar issues in the future. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** #COE-INC141103 **Incident Date:** April 20, 2026 ‌ **Summary** On April 20, 2026, between 12:30 PM PDT and 04:35 PM PDT, Autodesk experienced a service disruption that prevented BIM Collaborate Pro for Government users from loading projects. ‌ **Impacted Services** * BIM Collaborate Pro for Government ‌ **Root Cause** * A system configuration automatically limited the number of stored versions of a critical service component, which led to required versions becoming unavailable. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Additional alerting mechanisms to notify on-call engineers in real time. * Review of system configuration policies to prevent unintended removal of required service versions. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc141074-acs-locations **Incident Date:** April 20, 2026 ‌ **Summary** On April 20, 2026, between 1:40 AM PDT 8:25 AM PDT, Autodesk Forma customers creating new projects experienced failures in location-dependent functionality. ‌ **Impacted Services** * Build * Data Management * Takeoff ‌ **Root Cause** * Locations service upgrade caused an error upon creating new projects, due to incorrect environment variable. * The issue was resolved by restoring a previous version. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Enhancements to the validation process within non-production environments. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** # COE-INC140913 / #coe-inc140913-issues **Incident Date:** April 17, 2026 ‌ **Summary** On April 17, 2026, between 12:40 AM PDT and 10:57 AM PDT, Autodesk experienced a service disruption resulting in delays and failures during project creation for some customers in the Australia region. This issue affected customers using Forma Build, Forma Data Management, Forma Takeoff, and Forma AutoSpecs. ‌ **Root Cause** * A recent software change caused some project creation requests to keep retrying instead of stopping when they reached a permanent error condition. * As a result, some projects remained stuck in progress and customers saw delays or failures when trying to create new projects. * Autodesk resolved the issue by turning off the recent change in the affected region, which restored normal project creation. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Additional test coverage so similar project creation issues can be identified before release. * Monitoring and alerting improvements. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc140898-me-data **Incident Date:** April 17, 2026 ‌ **Summary** On April 17, 2026, between 8:19 AM PDT and 4:40 PM PDT, Autodesk experienced a service disruption affecting new customers creating and linking Flow Production Tracking \(FPT\) sites to the Flow Platform GraphQL API. Customers encountered failures during account creation, project setup, and role provisioning, preventing successful onboarding and use of Connected Workflows and GraphQL API functionality. The issue primarily impacted new customer onboarding in supported regions using Flow Platform GraphQL API and Flow Production Tracking \(FPT\). Existing customers and previously provisioned accounts were not affected. ‌ **Impacted Services** * Flow Platform GraphQL API * Flow Production Tracking \(FPT\) ‌ **Root Cause** * During onboarding, some newly created customer accounts were assigned an incorrect service configuration, which prevented successful role provisioning and site setup in Flow Production Tracking \(FPT\). * Autodesk identified the configuration issue, corrected the provisioning logic, and deployed the fix. Final validation confirmed that new customer onboarding was functioning normally. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Additional validation and logging to account creation and activation flows to improve issue detection and troubleshooting. * Improved monitoring and service visibility so similar onboarding issues can be detected and investigated more quickly. * Strengthened testing and validation processes to better identify provisioning issues before release. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** COE-INC140728 **Incident Date:** April 15, 2026 ‌ **Summary** On April 15, 2026, between 12:20 PM PDT and 3:02 PM PDT, Autodesk experienced a service disruption that prevented PlanGrid customers from saving edits to their Field Reports templates. ‌ **Impacted Services** * PlanGrid ‌ **Root Cause** * The issue was caused by recent changes to the Autodesk Build Forms backend, which is shared with PlanGrid Field reports. While these changes were correctly implemented in most parts of our system, the PlanGrid backend did not properly recognize them, which inadvertently affected PlanGrid Field Reports. * The fix was to update the PlanGrid backend to recognize the Autodesk Build forms changes. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Expanded test coverage of Autodesk Build Forms backend to detect any unintended impacts on the PlanGrid Field Reports product. ‌ Thank you for your patience and understanding.

**AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc140612-acc-autospecs **Incident Date:** April 14, 2026 ‌ **Summary** On April 14, 2026, between 12:15 PM PDT and 01:10 PM PDT, Autodesk experienced a service disruption impacting customers using Forma AutoSpecs within Forma Build and Forma for Construction Operations. ‌ **Impacted Services** * Forma AutoSpecs ‌ **Root Cause** The issue occurred when a large number of PDF files were uploaded at once, resulting in a high total file size. Processing these files required more system resources than were available at the time, which led to temporary service disruption. ‌ **Autodesk Actions** Autodesk has completed a review of the incident and is implementing the following improvements: * Increasing available system resources to better support large file processing * Introducing limits on the total size of files that can be uploaded at one time ‌ Thank you for your patience and understanding.