Major incident

Flexera System Status Dashboard: Spot- Push notifications errors

Affected: Spot API

Current status of Flexera System Status Dashboard: Operational — live Flexera System Status Dashboard status

Timeline

1. Sep 29, 2026, 11:08 UTC
   investigating
   Incident Description: We are investigating an issue affecting the event notification service across multiple production environments. Customers may experience delays or failures when receiving v2 event notifications, including notifications delivered through email, webhooks, Slack, and other supported channels. Events continue to be recorded and remain accessible through the Flexera One console and API. There is currently no indication that core platform functionality or event data has been impacted. Priority: P3 Restoration Activity: Our technical teams have identified the issue and implemented service recovery actions. Monitoring indicates that error rates are decreasing, and teams are continuing to validate service stability and assess the full scope of the impact. Further updates will be provided as the investigation and recovery efforts progress. Update: Further investigation confirmed that this issue did not impact customers. The affected notifications were not intended to be published.
2. Sep 29, 2026, 11:53 UTC
   resolved
   After closely monitoring the services to confirm stability, our teams observed no further errors or recurrence of the issue. This incident is now resolved.
3. Oct 13, 2026, 04:42 UTC
   postmortem
   **Description:** Spot by Flexera - Event Notification Processing Errors **Timeframe:** September 29, 2026, 2:06 AM PDT - 4:51 AM PDT **Incident Summary** On September 29, 2026, Flexera identified elevated application errors within a notification processing component responsible for handling certain event notification workflows. Automated monitoring detected increased error activity, prompting an investigation to determine whether customer-facing notifications were affected. During the investigation, technical teams identified failures occurring within a notification processing path and performed a detailed assessment of the affected events, notification workflows, and potential customer impact. Initial analysis suggested the issue could potentially affect notification processing more broadly, and a Major Incident was declared while the scope and impact were being validated. Further impact assessment confirmed that the affected notifications were not intended to be published to customers. Event information continued to be successfully recorded and remained available through the platform throughout the investigation. No customer-facing functionality was disrupted, no event data was lost, and no customer impact was identified as a result of this issue. Based on the results of the impact assessment, the incident priority was downgraded and the investigation was concluded after validation confirmed that customer-facing services remained unaffected. **Root Cause** Investigation determined that a notification processing workflow encountered an application exception while handling a subset of internally generated events. These events were configured such that they were not intended for customer notification delivery. Although the exceptions generated elevated application errors and warranted investigation, subsequent analysis confirmed that the affected notifications were not expected to be distributed to customers. As a result, customer-facing notification delivery, platform functionality, and access to event information were not adversely impacted. **Remediation Actions** The following actions were taken during the incident response: 1. Incident Investigation Initiated: Technical teams investigated elevated application errors detected through automated monitoring and assessed potential customer impact. 2. Notification Processing Analysis Performed: The affected notification workflow was reviewed to identify the source of the application exceptions and determine the scope of the issue. 3. Customer Impact Assessment Completed: Technical teams validated the affected notification types, reviewed event publication behavior, and confirmed that the notifications involved were not intended for customer delivery. 4. System Validation and Monitoring Conducted: Error trends, service behavior, and notification processing were monitored to confirm stable operation and validate that customer-facing services remained unaffected. 5. Incident Reclassification Completed: Following confirmation that no customer impact existed, the incident priority was downgraded and the incident was formally resolved. **Future Preventative Measures** Following this investigation, we identified opportunities to improve the speed and accuracy of impact assessment when operational alerts involve internal processing workflows. 1. Improved Impact Assessment: Review internal notification classifications and investigation procedures to accelerate determination of whether an issue affects customer-facing functionality during future incidents. 2. Enhanced Notification Workflow Visibility: Improve operational visibility into customer-facing and non-customer-facing notification processing paths to support faster impact validation and incident response activities.

Updates as published by Flexera System Status Dashboard (original).