Description: Flexera One IT Asset Management – EU – Reconciliation Failures

Timeframe: August 12, 2026, 5:50 PM PDT to August 12, 2026, 8:29 PM PDT

‌

Incident Summary

‌

On Wednesday, August 12, 2026, at 5:50 PM PDT , Flexera identified an issue affecting reconciliation process within the Flexera One IT Asset Management (ITAM) EU Production environment. During the impact period, Some reconciliation jobs experienced failures when they were assigned to a specific processing instance that had not completed its required configuration.

Initial investigation determined that the issue was isolated to a single server that did not complete its configuration successfully. As a result, the affected server was unable to establish communication with a required dependent service. Reconciliation jobs processed by this server failed, while jobs routed to other correctly configured processing servers continued to complete successfully.

Technical teams investigated the issue, identified the configuration discrepancy, completed the required connectivity configuration, and validated successful communication with the dependent service at 8:29 PM PDT. Following remediation, reconciliation processing resumed normally, affected workloads were reprocessed, and continued monitoring confirmed service stability. After monitoring the services to ensure stability , the issue was declared as restored at 10:56 PM PDT.

‌

Root Cause

‌

A batch processing server entered service with an incomplete configuration due to an initialization process that did not fully complete. As part of the required deployment sequence, network connectivity configuration must be established before the IT Asset Management processing components become available to process workloads.

Because the required connectivity configuration was not completed on the affected server, it was unable to communicate with a dependent reconciliation service. When reconciliation jobs were assigned to this server, processing failed, resulting in reconciliation failures for workloads routed through the misconfigured instance.

Contributing Factors

• The issue was isolated to a single batch processing server that did not complete its full initialization and configuration sequence successfully.
• The server became available to process workloads before all required connectivity configuration steps had been fully validated.
• Required service connectivity configuration was not fully established prior to the server entering normal processing operations.
• Impact was limited to reconciliation jobs routed through the affected server, while jobs processed by correctly configured servers continued to complete successfully.
• Existing deployment validation controls did not detect the incomplete configuration state before the server began processing customer workloads.

‌

Remediation Actions

‌

• Initialization Process Rerun: The failed initialization process was rerun successfully on the affected batch processing instance.
• Configuration Completion: All required post-installation configuration steps were completed, restoring the instance to the expected configuration.
• Connectivity Restoration: Connectivity between the IT Asset Management processing environment and the reconcile service was restored and validated.
• Service Validation: Teams confirmed that reconciliation failures had stopped occurring and continued monitoring the environment to verify stable operation.

‌

Future Preventative Measures

‌

• Deployment Sequence Improvements - Update deployment procedures to ensure processing services remain unavailable until all initialization and configuration activities have completed successfully.
• Post-Deployment Validation Enhancements - Implement additional validation checks to verify that all required configuration steps have completed before services enter production operation.
• Deployment Control Review - Review and strengthen deployment controls to ensure service startup sequencing and configuration requirements are consistently enforced across future releases.