Outsystems incident
Recurring issue Deployment Stage Incorrectly Ordered on ODC Platform
Outsystems experienced a major incident on June 30, 2026 affecting US East / Virginia and Europe / Frankfurt and 1 more component, lasting 9h 26m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 30, 2026, 08:56 AM UTC
We are investigating a recurring issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is currently affecting users across several regions. Our team is actively working to resolve the problem as quickly as possible and will provide updates as more information becomes available.
- monitoring Jun 30, 2026, 02:05 PM UTC
A fix has been implemented to address the configuration issue affecting deployment pipelines across multiple regions. We are now closely monitoring the platform to ensure application promotions are proceeding as expected and to confirm that all systems have fully recovered.
- resolved Jun 30, 2026, 06:22 PM UTC
The configuration issue affecting deployment pipeline stage ordering across multiple regions for ODC has been resolved. The fix has fully addressed both the primary issue identified on June 29th and a secondary edge case affecting users with custom environment names. Our team has completed the monitoring period, and all services are now operating as expected. We apologise for any disruption caused and thank you for your patience.
- postmortem Jul 02, 2026, 08:13 AM UTC
On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.