Autodesk incident

Forma Takeoff

Minor Resolved View vendor source →

Autodesk experienced a minor incident on May 13, 2026 affecting Forma Takeoff and Forma Takeoff (Australia) and 1 more component, lasting 15m. The incident has been resolved; the full update timeline is below.

Started
May 13, 2026, 09:44 PM UTC
Resolved
May 13, 2026, 10:00 PM UTC
Duration
15m
Detected by Pingoru
May 13, 2026, 09:44 PM UTC

Affected components

Forma TakeoffForma Takeoff (Australia)Forma Takeoff (Canada)Forma Takeoff (European Union)Forma Takeoff (Germany)Forma Takeoff (India)Forma Takeoff (Japan)Forma Takeoff (UK)

Update timeline

  1. investigating May 13, 2026, 09:44 PM UTC

    We are investigating an issue where customers are experiencing issues while attempting to export estimate reports from the Estimate tool within Forma Takeoff across multiple regions. We are actively looking into this and we will provide an update within 60 minutes or sooner if we have more information to share.

  2. resolved May 13, 2026, 10:00 PM UTC

    The issue has been resolved. Thank you for your patience and understanding as we worked to resolve this issue.

  3. postmortem Jun 01, 2026, 03:18 PM UTC

    **AUTODESK EVENT ANALYSIS** **Incident Number:** #coe-inc143157-reports **Incident Date:** May 13, 2026 ‌ **Summary** On May 13, 2026, between 11:45 AM PDT and 2:55 PM PDT, Autodesk experienced a service disruption that impacted customers exporting Estimate Line Item reports from the Estimate tool in Forma Takeoff across all regions. ‌ **Impacted Services** * Exporting of Estimate Line Item reports from the Estimate tool in Forma Takeoff in all regions. ‌ **Root Cause** * During a routine deployment of reporting services, an update to a shared reporting component was not fully compatible with Estimate Line Item report generation, which caused those reports to fail. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Additional automated tests to detect similar issues before future deployments. * Ensure future updates to shared reporting components are properly validated before release. ‌ Thank you for your patience and understanding.