Flexera One – SaaS Manager – NAM/APAC – Unable to Load Managed SaaS Applications

Update timeline

1. resolved Mar 27, 2026, 09:14 PM UTC

   Incident Description: An issue was identified that affected access to the Managed SaaS Applications page within the Flexera One SaaS Manager application. Customers encountered errors when attempting to load this page, impacting visibility into managed SaaS applications. Priority: P2 Impact Start Time: March 27, 2026, 12:37 PM PDT Impact End Time: March 27, 2026, 1:59 PM PDT Impact Duration: 1 hour 22 minutes Restoration Activity: The issue was traced to a subset of services supporting this functionality entering an error state. Corrective actions were taken, including restarting affected services and validating recovery across impacted regions. Full functionality has been restored, and the service continues to be monitored closely.

2. postmortem Apr 16, 2026, 06:21 AM UTC

   **Description:** Flexera One – SaaS Manager – NAM/APAC – Unable to Load Managed SaaS Applications **Timeframe:** March 27, 2026, 12:37 PM PDT to March 27, 2026, 1:59 PM PDT ‌ **Incident Summary** ‌ On Friday, 27th Mar 2026 at 12:37 PM PDT, an issue was identified that affected access to the Managed SaaS Applications page within the Flexera One SaaS Manager application. Customers encountered errors when attempting to load this page, resulting in a temporary loss of visibility into managed SaaS applications. During the impact window, customers in the NAM and APAC regions experienced errors when accessing the Managed SaaS Applications page. Users may have seen the error message: “An unexpected error occurred while loading managed applications.” The issue was limited to this specific functionality, and the rest of the Flexera One platform remained accessible and operational. No impact was observed in the EU region, and no customer cases were reported during the incident. Service was restored by restarting the affected component, which stabilized the impacted functionality, and normal operation resumed within the stated timeframe. ‌ **Root Cause** ‌ * The issue occurred due to a temporary disruption in communication with a supporting internal service required for application functionality. During this time, certain application components became unstable and were unable to process requests correctly, resulting in errors when loading the affected page. * The impacted service dependency was briefly unavailable but recovered after a restart, which restored normal operations. No code changes or permanent fixes were required. Contributing Factors: * Temporary unavailability of a supporting service dependency. * Limited resilience of affected components to short-lived connectivity interruptions. * Monitoring gaps, where alerts were triggered in one environment but not consistently across all affected components. * Minimal error logging, with only health check failures observed, which reduced early visibility into the issue. ‌ **Remediation Actions** ‌ The following remediation steps were implemented to restore service functionality: * Restored normal operation by restarting the affected supporting service. * Stabilized application components and verified successful page functionality. * Confirmed service health across impacted regions following recovery. ‌ **Future Preventative Measures** ‌ * Improved Service Resilience: Enhancing application behavior to better tolerate brief interruptions in dependent services without impacting user experience. * Enhanced Monitoring Coverage: Expanding monitoring to ensure consistent alerting across all environments and components. * Alerting Improvements: Reviewing and refining alert mechanisms to ensure issues are detected promptly and reliably across all clusters.