OutSystems Status

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.

Postmortem: 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.

Resolved: 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.

Investigating: 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 generally.

Our team is currently investigating the cause. We will provide an update as soon as more details are available.

Postmortem: On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.

The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.

To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.

To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Resolved: This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

Investigating: We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages.

Our team is currently investigating its cause. We will provide an update as soon as more details are available.