Outsystems incident
Incident affecting timer execution in US East / Virginia and Europe / Frankfurt
Outsystems experienced a minor incident on February 21, 2025 affecting US East / Virginia and US East / Virginia and 1 more component, lasting 1d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 21, 2025, 05:14 PM UTC
We are aware of an issue affecting timer execution. Customers may encounter errors when attempting to run a timer. Our development team has identified an impact on apps generated by Mentor. Our team is actively investigating the issue and working on a resolution. We will provide an update as soon as more details become available.
- monitoring Feb 21, 2025, 06:57 PM UTC
We have identified the cause of the issue affecting timer execution in portions of the US East / Virginia and Europe / Frankfurt regions. Customers in these regions may have experienced errors when executing timers. A workaround has been applied, and the issue is no longer manifesting. Our team is actively working on a permanent fix, which is currently under review and will be released as soon as possible. Monitoring is in place to detect and mitigate any recurrence immediately.
- resolved Feb 22, 2025, 08:03 PM UTC
The issue affecting timer execution in portions of the US East / Virginia and Europe / Frankfurt regions has been resolved. A fix was successfully implemented across all impacted environments, and timers are now functioning as expected. Monitoring and validation steps have confirmed that the issue is no longer present.
- postmortem Feb 25, 2025, 09:38 AM UTC
At 12:05 PM UTC, our monitoring detected the first signs of this issue. The first customer report was received at 12:53 PM UTC. The issue prevented timers from running in portions of two regions, affecting both customer applications and applications generated by Mentor. Further investigation revealed that a rare pattern in timer triggers was responsible. Corrective actions were applied, and by 6:30 PM UTC, all timers were confirmed operational. A permanent fix is being deployed to eliminate the risk of recurrence. In the meantime, enhanced monitoring is in place to detect this pattern early and enable rapid response if it reoccurs.