Flexera incident
Flexera One- IT Asset management & IT Visibility- APAC- Red Bar Error When Reconfiguring A Beacon
Flexera experienced a major incident on June 2, 2026 affecting IT Asset Management - APAC Beacon Communication and IT Visibility - APAC, lasting 14h 14m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 02, 2026, 07:41 AM UTC
Incident Description: We are currently investigating an issue affecting a subset of our customers in the APAC production environment who may encounter Red bar errors when attempting to reconfigure or redirect a Beacon . Priority: P2 Restoration Activity: Our technical and support teams havebeen engaged and they have identified that the issue is affecting multiple APAC production tenants. Initial investigations have ruled out several potential causes, and teams are continuing to analyze service dependencies and platform behavior to determine the root cause.
- identified Jun 02, 2026, 10:21 AM UTC
Our technical teams have identified a potential root cause for the issue and are actively working to implement and validate a fix. Investigation and remediation efforts remain ongoing, and teams are closely monitoring the environment throughout the implementation process. Further updates will be provided as they become available.
- identified Jun 02, 2026, 06:06 PM UTC
Technical teams have identified that the issue is likely related to a service compatibility issue affecting Beacon-related workflows in the APAC region. As part of the remediation effort, the team is validating a service update in lower environments before making any production change. The team is also continuing to review the contributing factors that led to the compatibility issue. We will provide another update as validation progresses.
- resolved Jun 02, 2026, 09:55 PM UTC
The issue affecting Beacon-related workflows in the APAC region has been resolved. Technical teams completed a service update, and validation has confirmed that the affected workflow is now accessible. We will continue to monitor the service to ensure continued stability.
- postmortem Jun 17, 2026, 05:21 AM UTC
**Description:** Flexera One – IT Asset Management and IT Visibility – APAC – Beacon Configuration and Reconfiguration Errors **Timeframe:** June 1, 2026, 7:41 PM PDT – June 2, 2026, 12:58 PM PDT **Incident Summary** On Monday, June 1, 2026, at approximately 7:41 PM PDT, an issue was identified affecting Beacon configuration and reconfiguration workflows in the APAC Production environment for Flexera One IT Asset Management and IT Visibility. During the affected period, customers attempting to access affected Beacon-related pages may have encountered a red bar error or server-side application error. Technical teams investigated the impacted workflows and backend service dependencies. The investigation confirmed that affected requests were returning server-side errors and that the issue was associated with the backend service supporting Beacon-related workflows. The issue was resolved by updating the affected Beacon API service in APAC Production. Following the update, the affected Beacon pages were confirmed accessible again. By Tuesday, June 2, 2026, at approximately 12:58 PM PDT, service was confirmed restored and the incident was considered resolved. **Root Cause** The incident was caused by a compatibility issue between the deployed Beacon API service version in APAC Production and recent IT Asset Management database changes. A required related Beacon API service update was not completed in APAC Production as part of the related release activity, which caused some Beacon configuration and reconfiguration workflows to return backend errors. These backend errors were surfaced in the UI as red bar errors when customers attempted to access affected Beacon-related pages. **Remediation Actions** The following actions were taken during the incident response: * **Impact Assessment:** Technical teams confirmed the issue was affecting Beacon configuration and reconfiguration workflows in APAC Production. * **Backend Error Isolation:** Investigation confirmed that affected requests were returning server-side errors from backend service dependencies. * **Service Compatibility Review:** Technical teams identified a compatibility issue between the deployed Beacon API service version and recent IT Asset Management database changes. * **Corrective Service Update:** The Beacon API service was updated in APAC Production to restore the affected workflows. * **Service Restoration Validation:** Following the update, technical teams validated that the affected Beacon pages were accessible and functioning as expected. **Future Preventative Measures** The following follow-up actions were identified: * **Strengthened Deployment Procedures:** We are strengthening deployment dependency checks and cross-team release coordination to ensure required service updates are clearly identified, tracked, and completed when related database or platform changes are released. * **Regional Version Alignment:** Related Beacon API service updates were completed across additional regions, including EU and NAM, to maintain version consistency and reduce the risk of similar compatibility issues occurring elsewhere. * **Expanded Post-Release Validation:** We are expanding post-release validation for critical Beacon configuration and reconfiguration workflows, especially when backend service or database changes are involved.