Flexera One IT Asset Management - NA - Batch Job Processing Delays

Update timeline

1. investigating Jun 03, 2026, 04:00 PM UTC

   Incident Description: We are investigating an issue affecting batch job processing for Flexera One IT Asset Management in the North America region. As a result, customers may experience delays in the completion of scheduled or queued batch processing jobs. Priority: P2 Restoration Activity: Our technical team is actively working to restore expected batch processing levels. Recovery actions are underway to increase processing capacity, reduce the current queue, and improve batch job processing throughput. We will continue to monitor progress and provide updates as recovery work continues.

2. identified Jun 03, 2026, 06:22 PM UTC

   Our technical team is continuing recovery work to restore expected batch processing levels. Additional processing capacity has been added to help reduce the current queue, and the team is continuing to review how queued jobs are being distributed for processing to improve overall throughput. Recovery efforts remain in progress, and we will continue monitoring the environment while work continues.

3. identified Jun 03, 2026, 08:46 PM UTC

   Our technical team is continuing recovery work to restore expected batch processing levels. Cleanup activities have been completed to reduce the current queue, and processing throughput is now improving. The team is continuing to monitor progress while recovery efforts remain in progress.

4. monitoring Jun 04, 2026, 02:52 AM UTC

   Our technical team has added processing capacity to improve batch processing throughput and reduce the remaining backlog. Additional processing capacity remains in place and is helping queued work continue to process. Processing activity has improved, and the backlog is continuing to decrease. The team is keeping the incident in a monitoring state while the remaining queued work clears and will continue tracking throughput and queue levels to confirm full recovery.

5. monitoring Jun 04, 2026, 07:45 AM UTC

   Processing activity continues to improve, and backlog levels are steadily decreasing. Our teams remain in a monitoring phase while the remaining queued work is processed and are continuing to track processing rates and queue volumes to validate sustained recovery. We will provide further updates as more information becomes available.

6. resolved Jun 04, 2026, 06:58 PM UTC

   Our technical team has confirmed that batch processing has recovered and is operating as expected. Earlier delays have been addressed, and queued work is now processing normally. We will keep monitoring the environment to ensure stability, and this incident is now resolved.

7. postmortem Aug 12, 2026, 02:23 AM UTC

   **Description:** Flexera One IT Asset Management \(ITAM\) - North America - Delayed Batch Processing **Timeframe:** June 2, 2026, 10:29 PM PDT - June 4, 2026, 6:29 AM PDT **Incident Summary** On June 2, 2026, following a scheduled production release in the North America production environment, customers using Flexera One IT Asset Management \(ITAM\) experienced delays in batch processing activities. After the release completed, technical teams identified that batch processing workloads were accumulating in processing queues and were not being executed at the expected rate. As the backlog increased, customers experienced delays in processing activities that relied on the ITAM batch processing platform. Technical teams immediately began investigating the issue and observed that processing capacity was not being utilized as expected. Additional batch processing capacity was temporarily introduced, workloads were reviewed and rebalanced, and non-critical processing tasks were reduced to help restore overall processing throughput. These actions resulted in a steady improvement in processing rates and a gradual reduction of the accumulated backlog. Throughout the recovery effort, technical teams closely monitored queue levels and processing activity while maintaining additional capacity to accelerate backlog reduction. Processing throughput continued to improve and queued workloads steadily decreased until normal operating conditions were restored. By June 4, processing backlogs had been cleared, remaining queued work was processing normally, and technical teams confirmed there was no longer any customer-facing impact. Following validation and continued monitoring, the incident was resolved. **Root Cause** Investigation determined that a release pipeline sequencing issue allowed infrastructure deployment activities to begin before a required release step had been completed. As a result, server instances became available earlier than intended during the production release process. This created conditions that led to abnormal batch processing behavior and the accumulation of processing workloads within the batch queues. The resulting backlog significantly reduced overall processing throughput and delayed execution of customer batch processing activities until mitigation measures were implemented and normal processing rates were restored. **Remediation Actions** The following actions were taken during the incident response: 1. Incident Investigation Initiated: Technical teams began investigating after identifying abnormal growth in batch processing queues following the production release. 2. Additional Processing Capacity Added: Additional batch processing instances were deployed to increase processing throughput and accelerate backlog reduction. 3. Workload Rebalancing Performed: Processing workloads were reviewed and rebalanced to improve utilization of available processing resources. 4. Queue Cleanup Activities Executed: Non-critical processing workloads were reduced to allow processing resources to focus on customer-impacting batch activities and improve overall processing throughput. 5. Continuous Monitoring and Validation: Technical teams continuously monitored queue levels, processing throughput, and backlog reduction until normal operating conditions were restored. 6. Release Pipeline Corrected: The release pipeline was updated to ensure required release steps are completed before infrastructure deployment activities can proceed. **Future Preventative Measures** Following the incident, changes were implemented to the release process to prevent the condition that contributed to this issue from occurring during future deployments. 1. Release Process Improvement: The release process was updated to ensure that critical deployment steps are completed in the correct order before server deployment activities begin. This prevents server components from starting earlier than intended and reduces the risk of similar batch processing disruptions during future releases.