Outsystems incident
Incident affecting timers LogMessage in ODC Portal
Outsystems experienced a minor incident on November 14, 2025 affecting Europe / Frankfurt and Asia Pacific / Tokyo, lasting 3d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 14, 2025, 02:26 PM UTC
We are aware of an issue concerning LogMessage entries not appearing in the ODC Portal when executed inside timers. This is affecting Europe (Frankfurt) and Asia Pacific (Tokyo) regions. Our team is currently investigating its cause. We will provide an update as soon as more details are available.
- identified Nov 14, 2025, 02:44 PM UTC
We have identified the cause of this issue. Our team is actively working on implementing a solution and we will provide an update once more details are available.
- monitoring Nov 14, 2025, 04:54 PM UTC
We have identified the cause of the issue. The fix is now in deployment, and a full resolution is expected by Tuesday, November 18th. We will continue monitoring this situation to ensure full recovery.
- resolved Nov 17, 2025, 05:45 PM UTC
We have successfully deployed a fix for the LogMessage issue that affected timers in the Europe (Frankfurt) and Asia Pacific (Tokyo) regions. Our monitoring confirms that the issue is fully resolved and all services are operating normally. Thank you for your patience.
- postmortem Nov 19, 2025, 09:04 AM UTC
A platform-wide issue was identified where log messages generated within successful Timers were inconsistently or completely missing from the monitoring interface. The root cause was a technical race condition during a critical component startup, which prevented logs from reaching the central logging system. Engineering team developed and deployed an update that resolved the issue, and extensive monitoring has confirmed the platform is now stable, with all Timer-originated log entries appearing correctly.