Flexera One - IT Visibility - US - Delayed Inventory Data Updates

Update timeline

1. investigating May 15, 2026, 05:11 PM UTC

   Incident Description: We are investigating reports of delayed updates for IT Visibility inventory data in the North America region. Some customers may observe recent inventory import activity showing a timeout status or delays in updated data becoming available within the application. Priority: P2 Restoration Activity: Our technical teams are actively reviewing the reported behavior to confirm the current scope of impact and validate customer-facing data availability. We are continuing to monitor the situation closely and will provide further updates as the investigation progresses.

2. investigating May 15, 2026, 06:44 PM UTC

   Our technical teams are actively reviewing the import processing workflow to identify where the reported timeout behavior is occurring and determine the appropriate remediation path. We are continuing to monitor the environment and will provide another update as the investigation progresses.

3. identified May 15, 2026, 10:13 PM UTC

   We have identified a potential underlying issue that may cause some IT Visibility inventory imports to show a timeout status. A fix has been put in place, and our technical teams are reprocessing affected inventory data. We are continuing to monitor progress and validate recovery. Further updates will be provided as reprocessing continues.

4. monitoring May 16, 2026, 07:32 AM UTC

   All uploads from the past days have now been processed successfully. Our teams will continue to closely monitor upcoming uploads over the weekend to ensure processing completes within expected timeframes and services remain stable.

5. monitoring May 17, 2026, 01:36 AM UTC

   We are continuing to monitor IT Visibility inventory data processing. During validation, additional processing errors were identified that are delaying completion for some inventory updates. Recovery efforts are continuing, and we are validating the remaining affected processing activity to confirm inventory updates complete successfully. We will continue to provide updates as recovery and validation continue.

6. monitoring May 17, 2026, 09:19 AM UTC

   Processing across all organizations has returned to normal, and the backlog has been fully cleared. New imports are now completing successfully, and the platform is operating within expected levels. Some customers may continue to see certain historical imports displayed as timed out in the UI. This is expected behavior for imports that exceeded the UI timeout threshold during the recovery period and does not necessarily indicate an active processing issue. Our teams continue to closely monitor the environment to ensure ongoing platform stability and successful processing of new imports.

7. monitoring May 18, 2026, 10:23 AM UTC

   Our teams continue to closely monitor the environment to ensure ongoing platform stability and the successful processing of new imports. A small subset of customers may continue to experience delays in the processing of new imports. Our technical teams are actively investigating the underlying cause of the slowness and are working to implement a resolution as quickly as possible.

8. monitoring May 18, 2026, 08:20 PM UTC

   Processing behavior has improved, and our teams continue to monitor the environment and validate recent import activity. Some previously affected imports are now processing successfully, and technical teams continue to review remaining slow-processing behavior to ensure new imports complete as expected. We will provide another update as validation continues.

9. monitoring May 19, 2026, 04:05 PM UTC

   Processing behavior continues to improve, and previously delayed inventory updates are continuing to progress. Our technical teams have made additional changes to improve processing performance and visibility. We are continuing to monitor progress, validate recent activity, and ensure inventory updates continue moving toward current processing. Further updates will be provided as validation continues.

10. monitoring May 20, 2026, 05:53 PM UTC

    We are continuing to investigate delayed IT Visibility inventory data updates. Our technical teams are reviewing the data ingestion process for affected inventory sources, as some updates are not being consistently received or reflected in the application. We are actively assessing the scope of impact and will provide further updates as more information becomes available.

11. monitoring May 21, 2026, 09:44 AM UTC

    Our technical teams continue to investigate reports of intermittent issues affecting certain uploads and ingestion activity. Current findings suggest this behavior may be related to a separate issue, though investigation and validation are still ongoing to determine the overall scope of impact. We will provide further updates as more information becomes available.

12. identified May 21, 2026, 10:37 PM UTC

    Our technical teams have made changes to the data ingestion flow, and initial validation shows recent inventory updates are moving through the expected processing path. We are continuing to validate recent activity and monitor for any remaining delays as processing continues. Further updates will be provided as validation continues.

13. identified May 22, 2026, 10:03 AM UTC

    Our technical teams continue to monitor the environment and validate recent inventory processing activity following the changes made to the data ingestion flow. At this time, we are awaiting further updates from the technical teams as investigation and validation efforts continue. Further updates will be shared as more information becomes available.

14. identified May 23, 2026, 10:21 AM UTC

    Our technical teams continue to closely monitor the environment and validate recent inventory processing activity following the changes implemented within the data ingestion flow. Investigation and validation efforts remain ongoing, and we are currently awaiting additional updates from the technical teams. Further updates will be provided as more information becomes available.

15. identified May 25, 2026, 12:00 PM UTC

    Our technical teams continue to actively investigate the issue while closely monitoring the environment and validating recent system activity following the implemented changes. Investigation and validation efforts remain ongoing, and we are currently awaiting additional findings and updates from the technical teams. Further updates will be shared as more information becomes available.

16. resolved May 26, 2026, 04:39 AM UTC

    Our investigation has been completed, and the issue has now been declared resolved based on current system behavior and validation results. Platform activity and processing have returned to expected levels, and our teams have confirmed stability across the broader environment. Based on current observations and available data, a small number of customers continue to experience isolated processing slowness. These cases appear to be limited in scope and are being tracked separately by the relevant technical teams, who are actively working toward resolution. At this time, no broader impact has been identified, and monitoring activities will continue to ensure ongoing platform stability.

17. postmortem Jun 10, 2026, 06:25 AM UTC

    **Description:** Flexera One - IT Visibility - US - Delayed Inventory Data Updates **Timeframe:** May 15, 2026, 8:40 AM PDT - May 25, 2026, 9:08 PM PDT **Incident Summary** On May 15, 2026, at approximately 8:40 AM PDT, we received customer reports of delayed IT Visibility inventory data updates in the North America production environment. The reports were received after a previous backlog-related incident had been closed. Some customers continued to observe inventory imports displaying a timeout status, while others reported delays in updated inventory data becoming available within the application. Technical teams investigated the reported behavior to determine whether the issue was related to residual processing activity from the previous incident, a recurrence of earlier processing delays, or a separate import status or processing concern. During the investigation, technical teams identified processing-related conditions that contributed to delayed completion for some inventory imports. This included processing slowness and errors in supporting services that could prevent some inventory processing activity from completing within expected timeframes. Corrective actions were applied to improve processing behavior, and affected processing activity was reviewed and reprocessed where needed. Technical teams continued validating reported customer examples and monitoring new inventory processing activity to confirm recovery. By May 28, 2026, at approximately 9:08 PM PDT, broader platform activity and processing had returned to expected levels, and the incident was considered resolved. **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 slowness and errors in supporting services. As a result, updated inventory data was delayed in becoming available within IT Visibility for some customers. In addition, some imports displayed a timeout status when processing took longer than expected. In some cases, this timeout status did not indicate that processing had stopped, 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 customer reports were received regarding timeout status behavior and delayed inventory data updates. 2. **Customer Reports Reviewed:** Reported customer examples and related support cases were reviewed to validate the scope and current behavior. 3. **Processing Activity Validated:** Technical teams reviewed inventory processing activity to determine whether timeout statuses reflected active processing delays or status behavior after processing had continued in the background. 4. **Processing Fix Applied:** A corrective fix was implemented for an identified issue that could contribute to timeout behavior, and affected processing activity was reprocessed. 5. **Supporting Service Errors Investigated:** Technical teams identified errors in supporting services that were contributing to delayed processing completion and engaged the appropriate teams for review and recovery. 6. **Processing Recovery Monitored:** Teams monitored affected processing activity and confirmed that delayed processing continued improving as recovery progressed. 7. **Customer Examples Validated:** Technical teams continued validating reported customer examples to confirm whether updated inventory data was progressing as expected. 8. **Post-Recovery Monitoring Performed:** Teams continued monitoring platform activity and inventory processing behavior before declaring the incident resolved. **Future Preventative Measures** This incident highlighted opportunities to improve visibility, monitoring, and recovery handling for IT Visibility inventory processing. The following follow-up areas are being reviewed: 1. **Inventory Processing Reliability:** Technical teams are reviewing improvements to strengthen inventory processing reliability and reduce the likelihood of similar delays. 2. **Monitoring and Observability:** Additional monitoring improvements are being evaluated to provide earlier visibility into processing delays, timeout patterns, backlog, and lack of processing progress. 3. **Import Status Clarity:** Teams are reviewing import status behavior to help reduce confusion when processing takes longer than expected but may still continue in the background. 4. **Operational Readiness:** Teams are reviewing operational improvements to support faster investigation, clearer internal visibility, and more consistent recovery handling for similar issues in the future.