Flexera One - IT Visibility - NA & EU - Inventory Processing Delays and Timeout Status

Update timeline

1. investigating Jun 02, 2026, 02:29 PM UTC

   Incident Description: We are investigating an issue affecting inventory processing in Flexera One IT Visibility. Customers may experience longer-than-expected inventory processing times, and some inventory imports may display a timeout status while processing continues. Priority: P2 Restoration Activity: Our technical team is actively investigating the issue and reviewing current processing activity to confirm scope and progress. We are monitoring the situation closely and will provide updates as more information becomes available.

2. investigating Jun 02, 2026, 06:10 PM UTC

   The team has identified examples where inventory uploads and collection activity completed successfully, but some results are taking longer than expected to finish processing and may continue to display a timeout status. Further review is ongoing to better understand the current processing state and overall scope. We are continuing to monitor progress and will provide another update as more information becomes available.

3. investigating Jun 03, 2026, 07:45 AM UTC

   Our teams continue to investigate the issue and review the current processing activity across the platform. While some operations are completing successfully, we are still assessing the extent of the impact and validating overall system behavior. Investigation and monitoring efforts remain ongoing as we work to better understand the underlying cause and identify any additional corrective actions that may be required. We will continue to provide updates as more information becomes available.

4. monitoring Jun 03, 2026, 08:50 AM UTC

   Services are operating currently. Our teams are monitoring backlog processing and collecting data to track progress and validate that queue volumes are decreasing as expected. We will continue to provide updates as more information becomes available.

5. identified Jun 03, 2026, 06:11 PM UTC

   The technical team has confirmed that the EU region is operating normally at this time, and processing activity appears stable. We will continue monitoring the EU environment to ensure it remains stable. Investigation and recovery efforts are continuing for North America, where some inventory imports may still display a timeout status while processing activity continues. The team is actively reviewing the remaining timed-out imports and tracking processing progress to confirm continued recovery. We will provide another update as more information becomes available.

6. identified Jun 04, 2026, 07:44 AM UTC

   Recovery and monitoring efforts remain ongoing in North America. While processing activity continues, some inventory imports may still show a timeout status. Our teams are actively reviewing the remaining affected imports and monitoring processing trends to validate continued recovery and system stability. We will provide further updates as additional information becomes available.

7. identified Jun 04, 2026, 06:47 PM UTC

   Recovery efforts remain ongoing in North America. Our technical team continues to review remaining inventory processing delays while monitoring processing activity and recovery progress. In parallel, we are continuing targeted work to improve the reliability and recoverability of IT Visibility inventory updates. We will provide further updates as recovery progresses and additional information becomes available.

8. identified Jun 05, 2026, 06:15 AM UTC

   Our technical teams continue to work on recovery efforts and monitor system performance. As part of the ongoing investigation, a corrective fix has been deployed to address a condition that may have contributed to processing delays and increased system load. Early monitoring is underway to validate the effectiveness of this change. While recovery activities continue, processing of the existing backlog is ongoing and may take additional time as the system works through queued activity. Teams are closely monitoring recovery progress and overall platform stability. We will continue to provide updates as more information becomes available.

9. identified Jun 05, 2026, 05:31 PM UTC

   Recovery efforts remain ongoing in North America. Our technical teams continue to monitor the corrective fix that was deployed to address a condition that may have contributed to processing delays and additional system load. Recovery progress continues to be impacted by underlying service instability. To support recovery, traffic has been adjusted while the affected service continues to stabilize. Processing of the existing backlog is ongoing, and some inventory imports may continue to take longer than expected while queued activity is processed. We are continuing to monitor recovery progress and overall platform stability, and will provide another update as more information becomes available.

10. identified Jun 05, 2026, 11:50 PM UTC

    The technical team has confirmed that the underlying service issue has stabilized, and the system has been scaled up to support recovery. A corrective fix has also been deployed for an issue that may have contributed to longer-than-expected processing times and timeout statuses. We are continuing to monitor inventory processing progress over the weekend to confirm continued recovery and stability. We will provide another update as monitoring continues.

11. monitoring Jun 06, 2026, 07:58 AM UTC

    Our teams continue to monitor recovery progress, and the service remains stable following the corrective actions implemented previously. We will continue to monitor processing and overall platform health over the weekend to confirm full recovery and will provide further updates as they become available.

12. monitoring Jun 06, 2026, 07:38 PM UTC

    Recovery progress continues to improve. The technical team’s latest review shows the number of inventory imports displaying timeout status has decreased compared to the previous review. The team will continue monitoring processing progress over the weekend to confirm continued recovery and stability. We will provide another update as monitoring continues.

13. monitoring Jun 07, 2026, 01:14 PM UTC

    Recovery efforts continue to show positive progress. Based on the latest review by the technical team, the number of inventory imports reporting timeout status has continued to decline and the backlog is steadily being reduced. The team will continue to closely monitor processing activity and platform stability to ensure recovery progresses as expected. We will provide further updates as additional information becomes available.

14. monitoring Jun 08, 2026, 12:39 PM UTC

    Recovery efforts continue to progress as expected. The latest review from the technical team shows the processing activity steadily reducing the remaining backlog. The environment remains stable, and teams are continuing to monitor processing throughput and platform health to confirm sustained recovery. Monitoring will remain in place until inventory processing has fully returned to expected levels. We will provide further updates as additional information becomes available.

15. identified Jun 08, 2026, 03:49 PM UTC

    Recovery efforts remain ongoing. The latest review shows that the number of inventory imports displaying timeout status has decreased overall compared to earlier recovery checks, although progress has been uneven while remaining queued activity is processed. The technical team has deployed an additional fix to improve processing behavior during recovery and is continuing to monitor its effectiveness. Teams are also continuing recovery actions to help remaining queued inventory processing move through the system. We will continue monitoring processing progress and platform stability, and will provide further updates as recovery continues.

16. identified Jun 09, 2026, 10:48 AM UTC

    Our teams continue to monitor recovery progress related to inventory processing delays and timeout status behavior. The recovery efforts continue to advance, with the number of remaining timed-out imports significantly reduced. Teams are reviewing the remaining impacted imports individually to ensure processing completes successfully. We are continuing to apply mitigation measures as needed, investigate the underlying factors contributing to the remaining delayed imports, and maintain enhanced monitoring to confirm continued recovery and full restoration of normal processing behavior. We will provide further updates as additional information becomes available.

17. monitoring Jun 10, 2026, 06:23 AM UTC

    The recovery efforts continue to progress, with only a very small number of imports remaining under investigation. The platform remains stable, and the vast majority of imports are processing successfully within expected timeframes. Teams are implementing additional improvements to further optimize processing capacity while continuing to monitor recovery progress and validate sustained platform stability. Enhanced monitoring remains in place as we work toward confirming full recovery and incident closure.

18. monitoring Jun 11, 2026, 09:07 AM UTC

    Further remediation actions have been implemented to speed up the process, and imports are no longer blocked for the organizations affected by the identified issue. Imports have successfully completed for some of the impacted organizations, while processing continues for the remaining organization and is expected to complete later today. The platform remains stable, with incoming imports processing within expected timeframes. The team has identified the probable root cause of the remaining issue and is actively working on a permanent fix. The current target is to complete deployment of the permanent fix next week, pending validation and release readiness.

19. monitoring Jun 12, 2026, 04:24 PM UTC

    Recovery has progressed significantly, and the platform remains stable. A workaround has been implemented for the imports affected by the remaining issue. Most of those imports have now completed successfully, and the remaining processing is being closely monitored. We will continue monitoring processing progress and provide further updates as available.

20. monitoring Jun 13, 2026, 04:09 PM UTC

    Recovery efforts continue to make strong progress, and the platform remains stable. The small number of remaining imports continue to process as expected and are being closely monitored by our teams. We will continue to track processing activity and recovery progress and will provide further updates as additional information becomes available.

21. monitoring Jun 15, 2026, 06:11 AM UTC

    Recovery efforts continue to progress, with only a very small number of imports remaining under investigation. The platform remains stable, and incoming imports are processing within expected timeframes. Our teams are actively reviewing the remaining exceptions to determine their causes and ensure successful completion. We will continue to closely monitor processing activity and platform performance and will provide additional updates as more information becomes available.

22. resolved Jun 16, 2026, 09:33 AM UTC

    The platform remains stable, and incoming imports are processing within expected timeframes. Any remaining import-related issues are being investigated separately as isolated cases . Based on the successful recovery and sustained platform stability, this incident has now been declared resolved. A post-mortem report containing additional details, including the root cause, remediation activities, and preventative measures, will be shared once the investigation is complete.

23. postmortem Aug 11, 2026, 01:06 AM UTC

    **Description:** Flexera One - IT Visibility - NA - Inventory Processing Delays and Timeout Status **Timeframe:** June 2, 2026, 7:29 AM PDT - June 15, 2026, 7:58 AM PDT **Incident Summary** On June 2, 2026, at approximately 7:29 AM PDT, we received customer reports of IT Visibility inventory imports displaying timeout status in the North America production environment. The ITV platform remained accessible during the incident. The primary customer impact was delayed inventory processing and delayed availability of updated inventory data for some customers. In some cases, imports displayed timeout status while processing was still pending or delayed. This status did not always indicate that processing had failed, as some processing activity could continue in the background and complete later. Technical teams investigated reported customer examples, reviewed organization and data source-level processing activity, and monitored backlog and processing progress over time. During the investigation, teams identified multiple contributing factors affecting timely inventory processing and recovery. These included processing inefficiencies that could add unnecessary load, conditions where processing progress could be delayed or regress during recovery, and temporary database instability that affected backlog reduction. Corrective actions were applied to improve processing behavior, stabilize recovery, and unblock affected processing activity. Technical teams continued monitoring timed-out imports, customer-reported examples, and new processing activity to confirm recovery. By June 15, 2026, at approximately 7:58 AM PDT, the broader incident impact had cleared. Remaining isolated items were isolated from the broader incident impact and continued to be tracked separately through follow-up actions. **Root Cause** The incident was caused by multiple contributing factors affecting the timely processing and availability of updated IT Visibility inventory data. Some inventory imports experienced delayed completion due to processing backlog and inefficiencies within the inventory processing flow. Identified defects contributed to unnecessary processing load and, in some cases, caused recovery progress to regress when services were restarted. Technical teams also identified conditions where queued processing activity was not always progressing as expected without recovery actions. In addition, temporary database instability impacted overall service recovery and slowed backlog reduction while the system was catching up. As a result, some imports displayed timeout status when processing took longer than expected. In some cases, the timeout status did not mean processing had stopped or failed, as processing could continue in the background and complete later. **Remediation Actions** The following actions were taken during the incident response: 1. **Incident Response Initiated:** Technical teams began investigating after multiple customer reports were received regarding inventory imports displaying timeout status. 2. **Customer Reports Reviewed:** Reported customer examples and related support cases were reviewed to validate the scope, affected organizations, data sources, and current processing behavior. 3. **Regional Scope Validated:** Technical teams reviewed timeout activity across regions. APAC did not show timeout activity, EU impact was limited and later narrowed, and the primary ongoing impact remained in North America. 4. **Processing Activity and Backlog Reviewed:** Teams reviewed inventory processing activity, backlog queues, organization-level processing state, and data source-level status to determine where imports were delayed and whether processing was still progressing. 5. **Database Recovery Supported:** Technical teams worked through database instability affecting recovery, including cluster recovery and scaling activity, to restore stability and improve backlog reduction. 6. **Processing Fixes Applied:** Corrective fixes were deployed for identified processing defects that could contribute to timeout behavior, unnecessary processing load, and recovery progress moving backwards during service restarts. 7. **Queued Processing Recovery Performed:** Teams applied recovery actions and workarounds to help queued processing activity move forward while the remaining processing issue was investigated and addressed. 8. **Affected Imports Unblocked:** Technical teams implemented a workaround to unblock affected imports for the remaining impacted organizations and continued monitoring those imports through completion. 9. **Customer Examples Validated:** Customer-reported examples were reviewed throughout recovery to confirm whether affected imports and updated inventory data were progressing as expected. 10. **Post-Recovery Monitoring Performed:** Teams continued monitoring platform activity, timed-out imports, and new processing behavior until the broader incident impact had cleared. Remaining isolated items were isolated from the broader incident impact and continued to be tracked separately through follow-up actions. **Future Preventative Measures** Following this incident, technical teams implemented improvements to strengthen the reliability, recoverability, monitoring, and operational visibility of IT Visibility inventory processing. The implemented improvements included: 1. **Inventory Processing Reliability and Recoverability:** Improvements were made to reduce conditions that could contribute to delayed processing, unnecessary processing load, or recovery delays when queued inventory activity needed to catch up. 2. **Monitoring and Observability:** Additional monitoring and observability improvements were implemented to provide better visibility into processing health, throughput, latency, failure patterns, retry behavior, and backlog accumulation across production environments. 3. **Recovery Handling:** Recovery processes were improved to help teams identify delayed or stuck processing activity earlier and take corrective action more consistently when processing did not progress as expected. 4. **Operational Readiness:** Internal investigation and validation processes were improved to help teams assess affected organizations, data sources, and processing state more efficiently during similar events. Teams also reviewed import status behavior to provide clearer status information when processing takes longer than expected but may still continue in the background. Since these corrective measures were implemented, we have not observed a recurrence of the same broad incident pattern.