Flexera One- IT Asset management- US - Degraded performance

Update timeline

1. identified Jul 22, 2026, 08:25 AM UTC

   Incident Description: We have identified an issue affecting inventory processing in Flexera One IT Asset Management following the deployment of the 2026 R1.1 release in our US production environment. As a result, some customers may experience degraded performance and intermittent reliability issues when accessing certain areas of the user interface and performing system-related tasks. Priority: P3 Restoration Activity: Our investigation has determined that the issue is related to a software defect introduced with the 2026 R1.1 release. While the defect had been previously identified and mitigation procedures were incorporated into the deployment process, the automated remediation encountered unexpected execution issues . As a result, technical teams have implemented alternative mitigation measures to reduce customer impact and stabilise system performance. We continue to actively monitor the environment and apply corrective actions to address the underlying defect and restore normal service operation.

2. identified Jul 22, 2026, 01:38 PM UTC

   Our teams continue to work on implementing a hotfix to address the issue . During deployment, the hotfix encountered database conditions that are preventing it from completing successfully. Our technical teams are actively working to resolve this and are evaluating targeted mitigation actions to allow the hotfix to complete. Once the hotfix has been successfully applied, teams will validate service performance and continue monitoring to confirm recovery. We will provide another update as more information becomes available.

3. monitoring Jul 22, 2026, 03:40 PM UTC

   The hotfix has been successfully deployed, and engineering teams are currently validating its effectiveness. Teams are continuing to monitor platform behaviour and review telemetry to confirm the issue resolution.

4. resolved Jul 22, 2026, 04:16 PM UTC

   Our teams have completed post-deployment validation and confirmed that service performance has returned to expected levels. Continued monitoring has shown stable platform operation with no further impact observed. Based on these results, this issue is now considered resolved.

5. postmortem Aug 04, 2026, 08:57 PM UTC

   **Description:** Flexera One – IT Asset Management – North America – Degraded Performance **Timeframe:** July 20, 2026, 8:13 PM PDT – July 22, 2026, 8:41 AM PDT ‌ **Incident Summary** On July 20, 2026, at approximately 8:13 PM PDT, an issue began affecting Flexera One IT Asset Management customers in the North America production environment following completion of the production release. During the affected period, some customers experienced intermittent application slowness, delayed processing, reconcile failures, timeout conditions, and degraded performance across inventory-related workflows. Technical teams investigated performance and reliability issues observed following the release and worked to determine the underlying cause and scope of impact. The investigation determined that the observed behavior was associated with a defect previously identified in the release. Corrective changes intended to address the defect were included as part of the release activity; however, the corrective changes did not successfully apply across all North America production databases during the deployment process. As a result, some environments continued to experience significantly increased database processing activity during inventory-related operations, contributing to elevated resource consumption, processing delays, timeout conditions, and degraded application performance. Technical teams worked to successfully deploy the corrective changes across the affected North America production databases. Following deployment, teams performed validation activities and monitored processing workflows to confirm recovery. By July 22, 2026, at approximately 8:41 AM PDT, validation confirmed successful processing of previously impacted workloads and that the previously observed failure patterns were no longer occurring. The incident was considered resolved and technical teams continued monitoring to confirm service stability. ‌ **Root Cause** The incident was caused by corrective changes intended to address a previously identified defect not successfully applying across all North America production databases during the release deployment process. As a result, the underlying defect remained active in affected environments and caused significantly more database processing activity than intended during inventory-related processing operations. This increased workload resulted in elevated resource consumption, processing delays, timeout conditions, and degraded platform performance. These conditions contributed to intermittent application slowness, delayed processing, reconcile failures, and degraded performance affecting some IT Asset Management functionality within the North America production environment. ‌ **Remediation Actions** 1. **Incident Investigation Initiated:** Technical teams investigated reports of application slowness, processing delays, reconcile failures, and degraded platform performance affecting the North America production environment. 2. **Impact Assessment Performed:** Teams reviewed customer-reported symptoms, system performance data, processing activity, and platform behavior to determine the scope and nature of the issue. 3. **Cause Identified:** Investigation determined that corrective changes intended to address a previously identified defect did not successfully apply across all North America production databases during the release deployment process. 4. **Processing Behavior Corrected:** Technical teams deployed corrections designed to eliminate the inefficient processing behavior that was contributing to elevated database workload, processing delays, timeout conditions, and degraded application performance. 5. **Recovery Validated:** Teams validated the effectiveness of the deployed changes through monitoring and successful execution of previously impacted processing activities. 6. **Post-Restoration Monitoring Performed:** Additional monitoring confirmed that the previously observed failure patterns and performance degradation were no longer occurring and that service stability had been restored. ‌ **Future Preventative Measures** Based on the investigation, the following follow-up activities have been identified: * **Processing Logic Improvements:** Technical teams implemented and validated corrective changes to the inventory-processing logic responsible for the increased database workload observed following the release. These changes were designed to eliminate the inefficient processing behavior that contributed to processing delays, reconcile failures, timeout conditions, and degraded application performance. * **Critical Hotfix Deployment Process Review:** Technical teams will review the deployment process for critical database hotfixes and evaluate alternative approaches to help ensure required corrective changes are successfully applied during future release activities.