BIM Collaborate (Australia) | Forma Design Collaboration (Australia)

Update timeline

1. investigating Jul 08, 2026, 05:49 AM UTC

   We are investigating reports where customers are unable to share packages in design collaboration of Forma in 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.

2. investigating Jul 08, 2026, 06:32 AM UTC

   We are continuing to investigate reports where customers are unable to share packages in the BIM Collaborate and Forma Design Collaboration in the Australia region. We will provide an update within 60 minutes or sooner if we have more information to share.

3. investigating Jul 08, 2026, 06:33 AM UTC

   We are continuing to investigate this issue.

4. investigating Jul 08, 2026, 07:37 AM UTC

   We are continuing to investigate reports where customers are unable to share packages in the BIM Collaborate and Forma Design Collaboration in the Australia region. We will provide an update within 60 minutes or sooner if we have more information to share.

5. investigating Jul 08, 2026, 08:32 AM UTC

   We are continuing to investigate reports where customers are experiencing an issue where Revit files shared via Design Collaboration in Forma remain stuck in a processing state in the Australia region. We will provide an update within 60 minutes or sooner if we have more information to share.

6. resolved Jul 08, 2026, 09:26 AM UTC

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

7. postmortem Jul 31, 2026, 09:17 PM UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** COE-INC148619 **Incident Date:** July 7, 2026 ‌ **Summary** On July 7, 2026, between 5:12 AM and 11:40 AM PDT, customers in the Australia region were unable to share and consume packages in Autodesk Forma Design Collaboration and Autodesk BIM Collaborate. Files published during this period remained in a processing state, and packages shared from them did not finish loading and returned an error, leaving them unusable. Model Coordination was also affected, as newly published model versions were not detected, and users remained on earlier versions. Publishing files into a project and other file management activity continued to work normally throughout the event, and no customer data was lost. ‌ **Impacted Services** * BIM Collaborate \(Australia\) * Forma Design Collaboration \(Australia\) ‌ **Root Cause** * A routine production update to the service that prepares published files for viewing was deployed with an incorrect configuration value, which pointed a processing component at the wrong internal resource. As a result, the step that generates the viewable data required to share and open a package stopped completing. * Because publishing itself continued to succeed, files appeared to upload and process normally while the viewable data was never produced. Design Collaboration and Model Coordination therefore held those files in a processing state rather than reporting an error, which is why the issue presented to customers as an indefinite processing indicator. * The update had been scheduled for a later release but was rolled out to all regions ahead of plan to resolve an unrelated issue in a third-party software library. Automated post-deployment checks did not cover this specific processing path, and the low overnight traffic volume in the Australia region meant the failure did not stand out on service dashboards, so the event was reported by a customer rather than detected by monitoring. * Autodesk rolled back the update at 11:40 PM PDT on July 7, 2026, which restored normal processing for newly published files. Files published while the issue was active had to be republished to generate their viewable data, and Autodesk worked directly with affected customers to complete that recovery. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified actions to be taken. These include the following: * Rolled back the configuration change during the event to restore normal file processing and reviewed the release so that updates of this kind are not rolled out ahead of their planned schedule. * Added end-to-end test coverage for this file processing path to our automated validation suite, so that a change affecting it is detected immediately after deployment rather than reported by customers. * Implementing automated alerting on the specific failure signal behind this event, so that our engineering teams are notified directly instead of relying on customer reports. * Improving error reporting within the affected processing component, and strengthening monitoring of processing volumes, so that a failure of this type is surfaced even during low-traffic periods in a single region. * Improving our ability to identify files left without complete viewable data after a disruption, so that they can be reprocessed without customers needing to republish them. ‌ Thank you for your patience and understanding.