Outsystems experienced a minor incident on June 25, 2026 affecting Europe / Frankfurt and Asia Pacific / Singapore, lasting 3h 47m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 25, 2026, 08:44 AM UTC
We are currently investigating an issue affecting users in Asia Pacific (Singapore) and Europe (Frankfurt). Affected users are experiencing failed application deployments to higher stages, accompanied by the error message OS-BLD-40303. Our team is actively working to resolve the issue, and we will provide further updates as they become available.
- identified Jun 25, 2026, 09:30 AM UTC
We have identified the root cause of the issue preventing application deployments and are actively working on a fix. Users in Asia Pacific (Singapore) and Europe (Frankfurt) may continue to experience failed deployments and encounter error message OS-BLD-40303 while the solution is being implemented.
- monitoring Jun 25, 2026, 11:36 AM UTC
We have applied a fix for the deployment issue and are currently monitoring the system to ensure full recovery. Users in Asia Pacific (Singapore) and Europe (Frankfurt) should see services returning to normal, and we will provide a final update once stability is confirmed.
- resolved Jun 25, 2026, 12:31 PM UTC
This incident has been fully resolved. Services are now operating as expected, and users can successfully deploy their apps without encountering the previous error.
- postmortem Jun 25, 2026, 01:15 PM UTC
On June 24th, an issue occurred that impacted ODC application deployments for non-administrator users across multiple regions, including Asia Pacific and Europe. Affected users experienced failures when attempting to deploy applications to higher stages and received an error during the build preparation step. Administrator accounts were not affected. The issue was caused by a configuration change deployed on June 23rd, which introduced a technical mismatch in how permission roles were validated within the build pipeline, preventing non-admin users from initiating deployments. The engineering team identified the root cause and reversed the change. Deployments are now functioning normally for all affected users. We are conducting a post-incident review to prevent similar issues from occurring in the future.