Outsystems incident

Incident affecting 1-Click Publish functionality

Resolved after 57 minutes, affecting US East / Virginia and Canada / Central and 1 more, on December 8, 2025.

postmortem Dec 11, 2025, 04:25 PM UTC

On December 8th, we experienced an issue that affected application publishing. This resulted in users being unable to publish any applications in the Development stage across all regions, encountering the error code OS-DPL-40802 \(Deployment timeout\). The root cause of the incident was a new version of an internal service that was deployed around the same time the problem started. This new version contained changes that caused application deployments to fail. The issue was resolved by reverting the internal service to the previous stable version.

Started
Dec 08, 2025, 10:15 AM UTC
Resolved
Dec 08, 2025, 11:12 AM UTC
Duration
57m
Detected by Pingoru
Dec 08, 2025, 10:15 AM UTC

Affected components

US East / VirginiaCanada / CentralSouth America / São PauloEurope / IrelandEurope / LondonEurope / FrankfurtIsrael / Tel AvivMiddle East / UAEAsia Pacific / MumbaiAsia Pacific / Singapore

Update timeline

  1. investigating Dec 08, 2025, 10:15 AM UTC

    We are aware of an issue impacting the 1-Click Publish (1CP) functionality. Customers may be experiencing error "OS-DPL-40802". This issue is affecting our customers in all regions. Our team is currently investigating the cause. We will provide an update as soon as more details are available.

  2. resolved Dec 08, 2025, 11:12 AM UTC

    This incident has been fully resolved and application deployments are now operating as expected. Our team will continue to investigate the root cause. Thank you for your patience.

  3. postmortem Dec 11, 2025, 04:25 PM UTC

    On December 8th, we experienced an issue that affected application publishing. This resulted in users being unable to publish any applications in the Development stage across all regions, encountering the error code OS-DPL-40802 \(Deployment timeout\). The root cause of the incident was a new version of an internal service that was deployed around the same time the problem started. This new version contained changes that caused application deployments to fail. The issue was resolved by reverting the internal service to the previous stable version.

Your product runs on more than Outsystems

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →