Description: Flexera One- IT Asset management - EU - Inventory upload errors
Timeframe: July 31, 2026, 6:00 PM PDT to August 4, 2026, 4:09 AM PDT
Incident Summary
On Sunday, August 2, 2026, at 11:42 PM PDT, Flexera identified an issue affecting inventory package (*.zip) uploads and select beacon communications within the Flexera One IT Asset Management EU Production environment. Affected customers experienced failed inventory package uploads, including HTTP 504 (Gateway Timeout) and HTTP 405 (Method Not Allowed) responses. The issue also disrupted select beacon-to-platform communications, causing delays or failures in inventory processing and inventory data ingestion.
The investigation determined that earliest impact started at 6:00 PM PDT on July 31st , 2026. Analysis identified a communication issue within a critical service routing path that prevented a subset of requests from successfully reaching downstream processing services. This resulted in repeated retries, delayed inventory processing, and backlog accumulation.
To mitigate the issue and restore service, traffic was redirected to an alternate communication path. Following this change, beacon communications stabilized, inventory uploads resumed processing successfully, and the inventory backlog began to decrease. By 3:42 AM PDT on August 3, 2026, inventory uploads were completing successfully and no new errors were observed.
The environment remained under extended monitoring while processing volumes returned to normal operating levels. At 4:09 AM PDT on August 4, 2026, Flexera confirmed that beacon communications, inventory processing, and associated platform services were operating normally, the backlog had returned to expected thresholds, and the incident was formally declared resolved.
Root Cause
On 31 July 2026, a certificate update to a critical service communication path created a configuration mismatch between platform components. The issue surfaced later, when application components were restarted and began establishing new connections using the updated configuration. This caused handshake errors and communication failures, resulting in service unavailability. Consequently, requests from customer beacons to upload inventory package (*.zip) files to the EU Production environment could not be processed, causing upload failures and preventing inventory data from being received and processed. A subset of other beacon-to-platform interactions was also affected, although customer impact was not observed immediately.
Service was restored by redirecting traffic to an alternate communication path that was not affected by the certificate-related configuration issue. Inventory uploads and beacon communications then resumed normal operation.
Contributing Factors
Intermittent Request Failures: Failed connection establishment attempts caused a portion of requests to be unsuccessful before reaching downstream processing services.
Inventory Processing Delays: Communication failures prevented some inventory packages and associated imports from processing successfully, resulting in delayed inventory updates.
Retry-Driven Backlog Growth: Automated retry mechanisms enabled many transactions to eventually succeed but contributed to increased processing delays and backlog accumulation while the issue remained active.
Remediation Actions
To restore service, technical teams performed below actions:
Traffic Re-routing: Redirected traffic away from the affected service path to restore stable beacon communications and inventory package uploads.
Platform Monitoring: Performed continuous monitoring of beacon communications, inventory uploads, and processing activity to verify service recovery.
Backlog Recovery Management: Monitored inventory processing throughput and validated that processing backlogs steadily reduced and returned to expected operating thresholds.
Stability Validation: Conducted extended monitoring following restoration to confirm sustained platform stability and successful inventory processing.
Service Restoration Confirmation: At 4:09 AM PDT on August 4, 2026, confirmed that beacon communications, inventory processing, and associated services were operating normally.
Future Preventative Measures
Service Communication Resilience: Review and enhance the affected communication path to improve reliability, resiliency, and recovery from future connectivity-related disruptions.
Strengthened Change Validation: Enhance validation and testing processes for infrastructure, configuration, certificate, and service-path changes to identify communication mismatches before deployment into production environments.
Improved Detection and Alerting: Enhance monitoring and alerting capabilities to provide earlier identification of sustained communication disruptions, elevated retry activity, abnormal error-rate patterns, and emerging processing backlogs. These improvements will enable faster detection, investigation, and remediation of issues before they develop into broader customer impact.