Flow Platform Permissions | Flow Platform Provisioning

Update timeline

1. resolved Jul 28, 2026, 01:07 PM UTC

   On July 28, 2026, at 03:30 AM PDT, Autodesk identified an issue where customers experienced latency while performing search queries and may have encountered stale data in Flow Platform Provisioning and Flow Platform Permissions. Once the issue was resolved on July 28, 2026, at 05:20 AM PDT, Flow Platform Provisioning and Flow Platform Permissions returned to normal operation. This is a retroactive notification as this issue did not display on the Autodesk Health Dashboard at that time. Thank you for your patience and understanding.

2. postmortem Aug 27, 2026, 09:30 PM UTC

   **AUTODESK EVENT ANALYSIS** **Incident Number:** # COE-INC151406 **Incident Date:** July 28, 2026 ‌ **Summary** On July 28, 2026, between 3:30 AM PDT and 5:20 AM PDT, Autodesk experienced an issue affecting the Search service due to capacity constraints in the Amazon MSK \(Kafka\) cluster supporting the service. The issue impacted the service’s ability to maintain the required number of Kafka consumer connections. ‌ **Impacted Services** * Flow Platform ‌ **Root Cause** * Autodesk completed a root cause analysis and determined that the issue was caused by a capacity limitation in the Amazon MSK \(Kafka\) cluster. * The cluster was configured with a default maximum client connection limit per broker. As the number of consumer connections increased, the service reached this limit, resulting in the incident. ‌ **Autodesk Actions** Autodesk has completed a post-incident analysis of the event and identified and implemented actions to improve capacity and prevent recurrence. These include the following: * Increased the maximum client connection limit to accommodate additional consumer connections. * Removed unused partner consumers from the configuration to reduce unnecessary Kafka connections. * Began development to split the ingestion service to reduce unused consumer connections and improve connection management. * Added monitoring and alerts to provide early notification when connection metrics approach configured limits. * Planned additional improvements to increase consumer utilization efficiency and further reduce the number of connections required to the Kafka brokers. ‌ Thank you for your patience and understanding.