Störungsverlauf von Outsystems

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.

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.

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.

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.

We are currently investigating an issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is affecting users across several regions. We are working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

The root cause has been found and linked to a misconfigured code that was deployed recently, which was then used to update the environment configuration orders. Mitigation actions will be implemented soon. We appreciate your patience while the fix is being fully rolled out.

We are continuing to work on implementing the fix for the configuration issue affecting deployment pipelines across multiple regions. While the mitigation actions are being executed, users may still experience issues promoting applications or see incorrect ordering in their deployment stages. We remain focused on resolving this as quickly as possible and will provide another update once the solution has been fully rolled out.

We are continuing to work on a fix for this issue.

We have applied a solution to resolve the configuration issue affecting deployment pipelines across multiple regions. We are now monitoring the platform closely to ensure that application promotions are functioning correctly and that all systems have fully recovered.

The incident has been resolved. The fix has been successfully applied across all affected regions, and we have verified that deployment pipelines are now operating with the correct stage ordering. We received direct confirmation from affected customers and have seen no further reports since the fix was implemented. We apologise for any disruption caused and thank you for your patience.

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.

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.

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.

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.

This incident has been fully resolved. Services are now operating as expected, and users can successfully deploy their apps without encountering the previous error.

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.

We are currently investigating an issue affecting ODC users in the US East (N. Virginia) region. Users are experiencing issues accessing applications in the DEV stage and may encounter an "Upstream Request Timeout" error. Our team is actively working to resolve the issue, and we will provide updates as more information becomes available.

We have applied a solution and are currently monitoring the situation to ensure a full recovery. ODC users in the US East (N. Virginia) region who were blocked from accessing applications in the DEV stage and encountering "Upstream Request Timeout" errors should see services returning to normal.

We are pleased to confirm that the incident has been resolved, and all services are now operating as expected. ODC users in the US East (N. Virginia) region should no longer experience issues accessing applications in the DEV stage or encounter "Upstream Request Timeout" errors.

On June 22nd, an incident affected ODC users in the US East \(N. Virginia\) region. Users were unable to access any applications in the Development stage, receiving an "Upstream Request Timeout" error. Production and Test stages, as well as all other regions, were unaffected. The incident was caused by a platform configuration change that prevented the component responsible for starting idle Development-stage applications on demand from functioning. As a result, when a request arrived, the application failed to start, causing the connection to time out at the gateway. The issue was resolved by reverting the configuration change. The component fully recovered, app startup resumed, and normal service operation was verified.

We have identified the cause of an issue affecting the Count parameter in advanced SQL queries. Customers may experience a runtime error (OS-BERT-60409 – Could not calculate the query count) and application crashes when using the Count parameter in advanced SQL queries. Additionally, we strongly recommend avoiding any redeployment or republishing of applications that use Advanced SQL in production until the issue is resolved, to prevent any potential unexpected behavior. Our team is actively working on a solution, and we will provide an update as soon as more details are available.

We have identified the cause of the issue affecting ODC and a fix is currently being deployed. Users may continue to experience symptoms while the update is being implemented. We are monitoring the progress closely and aim to have the issue fully resolved by 00:00 UTC on May 23rd.

We continue to deploy the fix for the issue affecting ODC and are seeing progress across the impacted services. Due to additional time required to complete the rollout safely and validate platform stability, the estimated resolution time has been updated to 07:00 UTC on May 23rd. Users may continue to experience intermittent symptoms while deployment activities are ongoing. We are closely monitoring the situation and will provide further updates as progress continues.

We continue to make progress on the deployment of the fix affecting ODC services. During the final stages of the rollout and validation process, additional time was required before pipelines could be safely unfrozen and normal operations resumed. The updated estimated resolution time is now 11:00 UTC on May 25th. Users may continue to experience intermittent symptoms while mitigation and validation activities remain in progress. We are actively monitoring the situation and will continue to provide updates as additional information becomes available.

A solution has been applied to resolve this issue. A republish of the application is required to fully apply the fix. We will continue monitoring this situation to ensure full recovery.

This incident has been fully resolved, and the Count parameter in advanced SQL queries is now operating as expected. To ensure you benefit from this fix, please make sure you republish the affected application and deploy it to the affected stage if necessary. Thank you for your patience and understanding while we worked to resolve this matter.

On May 22, 2026, we deployed an update intended to improve internal diagnostics. This update added automatic comments to generated SQL statements. In a specific edge case, where count-based queries were used inside nested SQL statements, these added comments disrupted the structure of the query and caused it to fail. Affected applications returned runtime errors and certain database queries could not complete successfully. After deploying a fix for this, services were restored and all affected queries are now functioning normally. We appreciate your patience while this was being resolved and remain committed to continuously improving the stability and reliability of the platform.

We are currently investigating an issue affecting O11 Personal Environments and ODC in the N. Virginia region. Customers may experience a variety of symptoms, most notably service unavailability for O11 and login/publishing issues for ODC. The cause has been identified to an issue in the AWS datacenter. We will provide an update as soon as more details are available.

We can now confirm that impact should only be perceived on O11 Personal Environments. AWS was able to identify that the issue was caused by a thermal event. Recovery might take several hours. We will continue to investigate this issue and closely monitoring the developments on the AWS investigations.

We have identified the root cause of the issue as a hardware failure within the AWS US East (N. Virginia) datacenter. We are actively deploying mitigations and closely monitoring AWS's recovery progress, which is expected to take several hours. Users may continue to experience symptoms while these fixes are being fully implemented.

We have now confirmation from AWS that access is now being restored on the affected environments. We suggest that customers can start testing on their end. Some customers might still face 504 errors or access issues. We continue to closely monitor the situation and we will provide further updates when available.

Based on official feedback from AWS as of May 8th, the core issue impacting ODC is mitigated and the service is now operating normally. For O11 Personal Environments, while the primary issue is resolved, some customers might still face 504 errors or access issues. A small number of instances remain impaired and AWS continues to work to recover all affected remaining resources. We will continue to closely monitor the situation and we will provide further updates when available.

This incident has been fully resolved, and Personal Environments in the N. Virginia region for O11 and ODC are now operating as expected. Thank you for your patience.

On May 8, 2026, at 12:03 AM UTC, ODC and O11 Personal Environments in the N. Virginia region experienced a service disruption caused by an AWS infrastructure event affecting a single Availability Zone. The disruption was related to an external power and cooling issue that impacted the availability of underlying AWS services. Customers experienced service unavailability, including issues with logging in and publishing applications.The impact was limited to O11 Personal Environments and a small subset of users, while impact on ODC remained contained. As AWS services recovered, many OutSystems environments resumed normal operation automatically. Some environments required additional recovery actions to fully restore service availability. For ODC, the incident was fully resolved on May 9, 2026, at 3:30 AM UTC. Recovery efforts for O11 Personal Environments continued afterward due to the additional complexity of restoring affected environments. All services are now operating as expected, and no user action is required.

We are experiencing some partial infrastructure outage which is causing connection issues with some of our online tools. We will update you as soon as we have the website up and running.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating an issue where users are unable to log into the ODC Portal. This issue is also impacting some functionality within ODC Studio. Affected users may encounter an error message stating they do not have the necessary permissions to see the content or that they cannot access the page. This incident is currently confirmed to be affecting all regions. We are working to identify the cause and will provide further updates as they become available.

The cause of this incident has been found. A new deployment of the Identity Services relied on a database schema that had not yet been updated, resulting in service unavailability and authentication failures, affecting all ODC regions. A solution has been applied by rolling back the deployment. The incident is now resolved, and services are operating as expected. We have confirmed that user applications were not affected during this time.

On April 13,2026 between 1:13 and 3:07 AM UTC, an incident occurred that prevented users from logging in to the ODC Portal across multiple regions. The issue was caused by a deployment of a Identity Service that required a database schema change that had not yet been applied, resulting in authentication failures. Service was restored after the team initiated a rollback to the previous stable version. Validation confirmed that login functionality was restored for all users. The incident is fully resolved, and all services are operating as expected.

We are experiencing some partial infrastructure outage which is causing connection issues with some of our online tools. We will update you as soon as we have the website up and running.

A fix has been implemented and we are monitoring the results.

The issues affecting our services have been resolved, and all systems are now operating normally. We apologize for any disruption this may have caused to your workflows.

We are currently investigating an issue affecting ODC. Users may experience errors when attempting to log into the ODC Portal and ODC Studio if they use External Identity Provider. Affected users are encountering the error message: "Email verification not supported / Email verification is not supported in the current Identity Provider. (OS-ID-BIZ-40302)". The current workaround is to reactivate the built-in identity provider. Please contact Support if you want to implement this option. Our team is actively working to identify the cause and restore full functionality.

We are continuing to investigate this issue.

A solution has been applied by rolling back a recent deployment of Identity Services, and our logs indicate that the errors have ceased. We are still investigating the root cause of this issue.

The incident is now resolved and login to ODC Portal and ODC Studio is operating as expected. The issue, which prevented a subset of users from logging in, was caused by a change intended to strengthen the email verification process. We have resolved the situation by rolling back to a previous version of the services and will perform a root cause analysis to prevent a recurrence in future releases.

On March 19th, 2026, at approximately 06:43 UTC, an issue was identified affecting ODC, where some users were unable to complete the login process for the ODC Portal and ODC Studio when using external Identity Providers. Affected users encountered an error message stating "Email verification not supported" or were blocked from accessing their accounts because the system could not verify their email addresses via the external provider's claims. The incident was caused by a configuration change intended to strictly enforce email verification from external providers. This change inadvertently bypassed a native fallback verification process that certain users relied upon when their external providers did not share specific verification data. The issue was resolved by 11:00 UTC on March 19th following a rollback to the previous service versions. To prevent recurrence, future updates to this functionality will be implemented via a gradual rollout plan, including additional validation steps to ensure all identity provider configurations are fully supported.

We are investigating an issue where users are experiencing errors when attempting to view application details within the ODC Portal. Specifically, users may encounter error code OS-CFGM-40060 during this process. Due to this behavior, users are unable to view or modify application configurations, which may prevent necessary updates or fixes to their applications. Our team is working to identify the cause and will provide further updates as they become available.

We have identified the cause of the issue affecting the viewing of application details. A recent configuration update created a validation mismatch between the ODC Portal and the underlying service. We are now working to revert this change to restore normal functionality. While we apply this fix, users may still encounter error OS-CFGM-40060 when accessing the View App detail page. We will provide further updates as the resolution progresses.

This incident has been fully resolved and application access in ODC Portal is now operating as expected. Thank you for your patience.

On March 4th, 2026, between 2:39 am and 10:29 am UTC, ODC experienced an incident that prevented users from accessing the App Detail screen and performing app configurations across all stages. The runtime of existing applications was not affected by this issue. The root cause was a subscription validation misalignment between internal APIs and ODC Portal, which resulted in errors for customers without the ODC Sentry add-on. To prevent future occurrences, we are updating ODC Portal to verify subscription status in alignment with these APIs and improving UI error handling to ensure failures like this do not obstruct the overall page experience.

We are currently experiencing service degradation in the Middle East (UAE) region due to connectivity and power issues within a major cloud provider (AWS). We are actively monitoring the situation and following updates from the official AWS status page. Our team is closely tracking recovery progress. We will provide further updates as more information becomes available.

AWS Team has identified the cause of the disruption affecting one availability zone in the Middle East (UAE) region. Power was temporarily shut down at the facility as a safety precaution. Restoration of power and connectivity may take several hours. Other availability zones in the region remain operational. We will provide further updates as more information becomes available.

We are continuing to monitor the official AWS status page. At this time, AWS has informed customers that some may experience errors when performing certain network-related actions. AWS is actively implementing mitigation measures, and recovery is expected within the next few hours.

Our services have been fully restored, and the issue affecting our OutSystems customers has been mitigated. While the ongoing disruption reported by AWS continues, it is not expected to impact our customers at this time. We will continue to closely monitor the situation. If you experience any issues, please contact our Support team. For updates directly from AWS, please visit: https://health.aws.amazon.com/health/status

We are currently investigating this issue.

We are investigating an issue affecting Outsystems Products in the Middle East (UAE) region. This disruption is related to the ongoing AWS service incident reported on March 1st. Users in this region are currently experiencing a total service outage in ODC, and all services are unavailable. We are monitoring the situation closely and will provide updates as more information becomes available.

We continue to follow closely the investigation in partnership with AWS, towards the recovery of the Middle East (UAE) Region. At this point, we are expecting recovery to take at least a day given the significant efforts required. Until then, ODC and other services in this region will continue experiencing a total service outage. We continue to monitor the situation closely and will provide updates as more information becomes available.

We are still continuing to monitor the investigation with AWS, as the recovery towards the impaired AWS Middle East (UAE) Region is still ongoing. While there have been significant improvements made so far, the estimated recovery time will take at least another day before power and connectivity can be restored.

The cause has been identified as a widespread infrastructure failure in the Middle East (UAE) affecting foundational AWS services. While recovery efforts are underway, ODC and other services in this region will remain unavailable until the underlying infrastructure is fully restored. We are closely monitoring the situation as it recovers and will provide further information once it becomes available.

Recovery efforts are still being prioritized by AWS for this region, focusing on restoration of the impacted AWS Services. We are closely monitoring the situation and will provide further updates once they become available.

Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

We are continuing to monitor the recovery of ODC services in the Middle East (UAE) as the underlying infrastructure issues are being addressed. We will provide further updates as soon as more information becomes available.

Recovery efforts are still underway for the Middle East (UAE) as cloud services work to restore one of the affected areas. We are continuing to track the progress and will provide further updates as more information becomes available.

Recovery efforts for the Middle East (UAE) region remain ongoing as cloud infrastructure providers work to restore impacted services. We continue to track the recovery progress and will provide further updates as more information becomes available.

Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are closely tracking the progress and will provide further updates as more information becomes available.

Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are continuing tracking the recovery process of this incident to ensure a complete recovery. Going forward, updates will be delivered directly to affected users through their individual support tickets. Users who require further assistance with this event are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

We are investigating reports of service disruption affecting O11 Cloud customer in the Middle East (Bahrain) region. We are currently reaching out to impacted customers directly and will provide further updates as more information becomes available.

Most affected O11 Cloud customers in the Middle East (Bahrain) region have been mitigated, and overall stability has improved. The AWS outage remains ongoing. We are continuing to actively monitor AWS updates to ensure full service recovery. Further updates will be provided directly to affected users via their individual support tickets. Customers requiring additional assistance are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

All customers impacted by this incident have been contacted and supported individually. While the Middle East region continues to be affected by the ongoing geopolitical situation and AWS continues to report the region as impacted, OutSystems has completed its direct response to every affected organization. The affected services remain flagged as a major outage while these conditions persist. Customers who need further assistance can contact OutSystems Support by raising a new ticket or continuing their existing case through Support Services.

We are investigating an issue in ODC affecting users in Europe (Frankfurt), Europe (London), and Israel (Central). Affected users may experience login failures when attempting to access their applications. Our team is currently working to address the situation.

We have confirmed that no additional users are being impacted at this time. Our team is continuing to investigate the situation to determine the full scope and cause.

We are continuing to investigate this incident. Our technical teams are actively working to identify the root cause, and we will provide further information as soon as it becomes available. We appreciate your patience as we work toward a resolution.

The cause of this issue has been identified and our team is currently working on a resolution. Users may continue to experience login failures while our team works on developing a fix.

This incident has been fully resolved and the applications login is now operating as expected. Thank you for your patience.

On January 30th, several ODC customers experienced intermittent issues where the username attribute was missing data from the User entity within applications. The cause was identified as a bug in a recent release of an identity component. This issue prevented specific user and identity provider data from correctly populating the Username Attribute. The incident was resolved by rolling back the affected release. A corrected version has since been deployed to ensure consistent data availability and prevent future occurrences.

We are currently investigating an issue where Mentor is unavailable for users in Asia Pacific (Singapore) and Europe (Frankfurt). This disruption is due to an underlying service outage with an external provider and may also impact users in other regions that rely on these services. Our team is actively working to address the situation.

As per additional investigation from our team, we detected that Mentor is unavailable for users in EMEA and APAC-based regions. We are continuing to investigate this issue.

We continue to investigate Mentor's unavailability for users in EMEA and APAC-based regions. We will provide an update as soon as more details are available.

While we await updates from our infrastructure provider, our teams are actively developing a fallback plan to mitigate the impact, through a non-affected region to restore functionality.

The incident affecting the ODC Mentor has been resolved, and all services are now operating normally. On January 27th, ODC Mentor experienced a service disruption. This was caused by an outage with an external cloud provider. We mitigated the impact by implementing infrastructure changes to bypass the affected provider services.

On January 27th, we experienced a service disruption in Mentor affecting APAC and EMEA regions. Users encountered elevated error rates and a loss of functionality for Mentor features. The incident was triggered by a third-party service outage, which hosts the models supporting our Data & AI services. While a fallback system was in place, it also became unavailable during the outage. Furthermore, the impact of the external service disruption also prevented our team from implementing a manual configuration fix immediately. We are also working toward an automated fallback mechanism to minimize the need for manual intervention. Additionally, we are implementing agent-level fallbacks to different models at the product level.

We are aware of an issue affecting 1-Click Publish feature in Europe Central region (Frankfurt). Customers in this region may experience a build timeout in publish operations. Our team is currently investigating its cause. We will provide an update as soon as more details are available

A solution has been applied to resolve this issue. We are now monitoring to ensure full recovery.

This incident has been fully resolved and the 1-Click Publish feature is now operating as expected. Thank you for your patience.

On January 22nd, between 15:00 UTC and 17:00 UTC, an incident affected ODC in the Europe \(Frankfurt\) region. Users experienced issues with One-Click Publish, specifically resulting in build timeouts and publish failures. The issue was caused by a communication failure between the internal queuing system and the Build Service, which prevented build processes from completing. Our team resolved the incident by restarting the Build Service and restoring communication. Normal service has been restored, and we are evaluating measures to improve system resilience moving forward.

We are aware of an issue where customers are unable to log into applications. Customers may encounter an “invalid redirect URI” error when attempting to log in to an application using a newly configured custom domain. Our team is currently investigating the cause of this issue and will provide updates as more information becomes available.

The cause of the issue has been identified, and a solution is being applied. Customers may still experience an “invalid redirect URI” error when attempting to log in to an application using a newly configured custom domain. Our team is actively working on the solution. We will provide an update once more details are available.

A solution has been applied to resolve the issue. Customers who are still experiencing problems with newly configured custom domains should follow these steps: 1. Delete the affected custom domain in the ODC Portal. 2. Remove the corresponding CNAME entries from your DNS provider and wait ~5 minutes. 3. Recreate the custom domain in ODC Portal and add the new CNAME records. 4. Once the status shows Active, try logging in again. If you continue to experience issues after following these steps, please contact us via Support Portal. We will continue monitoring the situation to ensure full recovery and will provide updates if any further action is required.

This incident is now fully resolved. If you continue to experience issues, please follow the steps shared in our previous communication. Thank you for your patience and understanding.

On January 16th, a service change related to an ongoing migration caused a temporary issue where customers were unable to log in using their custom domains. Our engineering team immediately identified the cause and implemented a mitigation to resolve the issue quickly by temporarily disabling the custom domain redirection feature. A controlled restart of system deployments was performed to expedite this fix. To ensure stability and prevent recurrence, a technical recommendation has been made to enhance the system. This improvement will increase resilience to future updates and configuration changes, helping maintain continuous operation without service interruptions.

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.

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

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.

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.

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.

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.

We are currently investigating an issue affecting a subset of Personal Edition users. Some users are seeing a “no permissions” message after signing in. Our team is actively working to identify the cause, apply mitigation for impacted users, and continue monitoring the situation closely. We will share an update as soon as more information becomes available.

We have identified the root cause of the issue affecting Post-Login Permissions for Personal Edition users. Some customers may still experience a “no permissions” message after signing in. Our team is actively working on a solution, and we will provide an update as soon as more details are available

We have successfully applied a manual fix for the Personal Edition users who reported the “no permissions” error; access for these accounts has been restored. Regarding other affected users who did not submit a report, we have sent a dedicated communication to your registered email address with further details. We will continue to monitor the system to ensure stability.

On November 26th, an issue was experienced affecting Personal Editions users, resulting in users seeing a “no permissions” page and being unable to use their Personal Edition environments. Normal service was restored at 21:00 UTC. The incident was caused by the reconfiguration step used to fix an earlier issue. This step correctly re-applied the Identity Provider \(IdP\) but also unintentionally made the affected Personal Editions environments available for re-assignment. As a result, many of the previously fixed Personal Editions were re-assigned to "second" users who were created without any permissions upon first login, leading to the “no permissions” screen. To prevent new occurrences, all Personal Editions environments created during the faulty period that had gone through the reconfiguration were discarded. Impacted users were proactively informed and instructed to request a new Personal Edition.

We are currently investigating an issue preventing some ODC Personal Edition users from logging in. Affected users may see the error message “Incorrect username or password (OS-UAUC-60004)” even when using their correct community credentials. Our team is actively working to identify the cause. We will share an update as soon as more information becomes available.

We experienced an issue that prevented some users from logging in to their Personal Editions across multiple regions. This affected tenants created between November 17 and 18 and assigned on November 22. The problem was caused by an incomplete internal configuration during setup, which blocked the login process. Our team has corrected the configuration for all affected tenants, and access has now been fully restored. Thank you for your patience while we resolved this issue.

On November 25th, around 11:15 UTC, we experienced an issue affecting Personal Editions, resulting in users being unable to log in and consistently seeing the error “Incorrect username or password \(OS-UAUC-60004\)” despite using valid credentials in the regions of US East \(Ohio\), Europe \(Ireland\), and Asia Pacific \(Singapore\). Normal service was restored by approximately 17:00 UTC the same day. The incident was caused by an issue in provisioning that led Personal Editions to not have the built-in community provider configured as an Identity Provider. This resulted in the login failures when users attempted to access their Personal Editions. To prevent new occurrences, the provisioning logic was updated to treat a similar empty response as an error, triggering an internal alert and preventing affected environments from being handed out as ready-to-use. Additionally, a targeted reconfiguration job was run to correctly apply the required identity provider to all impacted Personal Editions, which restored normal login functionality