Major incident

Flexera System Status Dashboard: Flexera One - IT Asset Management - EU & APAC - Inventory Processing Delays

Affected: IT Asset Management - EU Inventory Upload, IT Asset Management - APAC Inventory Upload

Current status of Flexera System Status Dashboard: Operational — live Flexera System Status Dashboard status

Timeline

1. Sep 18, 2026, 13:03 UTC
   investigating
   Incident Description: We are investigating an issue affecting inventory data processing in the EU and APAC production environments. Customers may observe delays in inventory updates, resulting in inventory data not reflecting the most recent import activity. Priority: P2 Restoration Activity: Our technical teams are actively investigating the issue, validating the scope of impact, and working with relevant dependencies to restore normal inventory processing. Further updates will be provided as more information becomes available.
2. Sep 18, 2026, 13:50 UTC
   identified
   Our technical teams have traced the issue to a recent deployment and have implemented remediation actions. Initial validation indicates inventory processing has resumed, and technical teams are actively monitoring processing activity and backlog recovery. We are continuing to validate recovery across the affected environments and will provide further updates as more information becomes available.
3. Sep 18, 2026, 14:34 UTC
   identified
   Technical teams have completed the required configuration updates, and inventory data continues to be processed successfully. Additional processing capacity has been allocated to accelerate backlog recovery, and technical teams are actively monitoring throughput and backlog reduction across the affected environments. Recovery activities remain in progress, and further updates will be provided as backlog processing continues.
4. Sep 18, 2026, 14:39 UTC
   monitoring
   Inventory data processing continues to recover, and technical teams are observing a downward trend in backlog volume. Additional processing capacity remains in place, and recovery progress is being closely monitored across the affected environments. We will continue to monitor backlog reduction and provide further updates as recovery progresses.
5. Sep 18, 2026, 18:52 UTC
   monitoring
   Inventory data processing continues following the previously implemented remediation. Technical teams are actively monitoring processing throughput and backlog recovery across the affected environments. Technical teams are continuing to assess recovery progress and any additional actions that may help accelerate backlog processing. Further updates will be provided as recovery progresses.
6. Sep 18, 2026, 19:49 UTC
   monitoring
   Backlog recovery has completed in APAC following the previously implemented remediation, and inventory data processing has returned to expected levels in the region. Recovery activities continue in EU, where technical teams are monitoring processing throughput and backlog reduction. Additional recovery measures are being evaluated to support backlog processing as recovery progresses.
7. Sep 18, 2026, 21:55 UTC
   monitoring
   Recovery efforts continue in EU, and technical teams are observing ongoing reduction of the remaining backlog. Additional recovery optimizations have been implemented to support backlog processing in EU, and technical teams continue to monitor throughput and overall recovery progress. Further updates will be provided as progress continues.
8. Sep 19, 2026, 11:07 UTC
   monitoring
   Recovery continues to progress, with the remaining backlog steadily decreasing. Additional optimisations implemented in the EU environment are supporting backlog processing effectively. Our teams continue to closely monitor recovery progress and will provide further updates as appropriate.
9. Sep 19, 2026, 19:09 UTC
   monitoring
   Recovery efforts continue in EU, and technical teams are observing continued reduction of the backlog following the previously implemented optimizations. Based on current recovery trends, backlog levels have been significantly reduced and continue to move in the expected direction. Further updates will be provided as progress continues.
10. Sep 20, 2026, 19:55 UTC
    resolved
    Technical teams have confirmed that inventory data processing in EU has returned to normal operation following the previously implemented remediation. The issue was traced to a deployment configuration issue affecting inventory data processing. The required configuration updates were applied, restoring normal processing. Following validation and extended monitoring, backlog recovery in EU has completed and inventory processing remains stable across both EU and APAC. This incident is now considered resolved.
11. Oct 23, 2026, 17:20 UTC
    postmortem
    **Description:** Flexera One - IT Asset Management - EU & APAC - Inventory Processing Delays Following a Deployment Configuration Issue **Timeframe:** September 16, 2026, 2:00 PM PDT - September 20, 2026, 9:52 AM PDT **Incident Summary** On Friday, September 18, 2026, technical teams began investigating reports of delayed inventory updates affecting Flexera One IT Asset Management \(ITAM\) customers in the Europe \(EU\) and Asia-Pacific \(APAC\) regions. Updated inventory information was not being reflected in the application, with some customers reporting that their latest available inventory data remained dated September 16. The issue affected inventory processing rather than general availability of the ITAM platform. Initial analysis indicated that the inventory-processing services appeared healthy, but incoming inventory files were not progressing through the expected processing workflow. Further investigation traced the interruption to a deployment performed on September 16, during which a configuration issue affected the services responsible for processing inventory data. Technical teams identified and corrected the deployment configuration, allowing inventory processing to resume. However, a significant backlog of inventory files had accumulated during the interruption and required additional time to process. Inventory processing recovered first in APAC, where the accumulated backlog was cleared on September 18 at approximately 12:21 PM PDT. The EU region required additional recovery time due to the volume of outstanding files. Technical teams adjusted processing capacity settings and continued monitoring the backlog as inventory files were processed. The remaining EU backlog was fully cleared on September 20 at approximately 9:52 AM PDT. Subsequent monitoring confirmed that inventory processing had returned to normal operating levels. **Root Cause** The incident was caused by a deployment configuration issue introduced during a September 16 update to the inventory-processing services. At the time of the deployment, the inventory-processing infrastructure was transitioning between application environments, with different services required to remain active in each environment depending on the region. This increased the complexity of maintaining the correct production configuration, and the required service configuration was not correctly maintained during the deployment. As a result, the inventory-processing workflow was interrupted in the EU and APAC regions, preventing incoming inventory files from being processed and delaying inventory data updates. Once the configuration was corrected, inventory processing resumed, with the accumulated backlog requiring additional time to process before normal operating levels were fully restored. **Remediation Actions** The following actions were taken during the incident response: 1. **Incident Investigation Initiated:** Technical teams investigated reports of delayed inventory updates in the EU and APAC regions and reviewed the inventory-processing workflow to identify the source of the interruption. 2. **Deployment Configuration Issue Identified:** Investigation traced the interruption to the September 16 deployment and identified an incorrect service configuration affecting inventory processing across the impacted regions. 3. **Production Configuration Corrected:** The required configuration updates were applied to restore the affected inventory-processing services, allowing incoming inventory files to resume processing. 4. **Inventory Backlog Recovery Initiated:** Technical teams monitored the accumulated inventory files and adjusted available processing resources to support backlog recovery following restoration of the processing workflow. 5. **Processing Throughput Optimized:** During EU recovery, technical teams identified processing capacity constraints under the increased workload and adjusted processing concurrency to improve throughput while maintaining ser

Updates as published by Flexera System Status Dashboard (original).