Intermittent disruptions to few features in Community region

Update timeline

1. resolved May 25, 2026, 09:46 AM UTC

   Between 21 May 2026 09:00 UTC and 25 May 2026 09:00 UTC, customers on the Community(Europe) region experienced intermittent disruptions to certain features like Solution install and uninstall and Studio Web Debug. Full impact scope is still being validated. The issue was traced to an internal configuration change in a UiPath service and has since been corrected. Service is operating normally.

2. postmortem May 27, 2026, 12:27 PM UTC

   ## Customer Impact Between May 21, 2026, 09:00 UTC and May 25, 2026, 09:00 UTC, a very small subset of customers in the Europe region saw intermittent failures across several Automation Cloud features: * Solution install and uninstall timeouts * Studio Web debug sessions failing to start or complete * UiPath Agents and Maestro jobs stuck waiting on Action Center task completion * Folder synchronization issues across Solutions, Notifications, LLM gateway, and related cloud platform services * User licenses not deallocating after assignment changes All other regions were unaffected. ## Root Cause On May 21 at 09:00 UTC, a planned infrastructure migration transitioned an internal messaging service to a new deployment environment. During the migration, a required runtime configuration governing downstream subscription handlers was not carried over correctly. As a result, certain handlers were treated as inactive, causing related events to be dropped. These subscription handlers support several internal services. Depending on the affected service functionality, some operations experienced delays, timeouts, or completed in an inconsistent state. ## Detection The first signals came from support tickets about Solution install/uninstall timeouts and from internal users hitting Studio Web debug failures. Automated alerts for elevated Solutions errors did fire, but at a non-critical severity, and the symptoms looked feature-specific rather than like a messaging-events layer issue. Because the failures were distributed across several seemingly unrelated features, correlating them back to the messaging migration took longer than it should have. The customer-facing status page entry was published retrospectively, after the cause was understood and corrected. ## Resolution On May 25 at 09:00 UTC, we applied the missing configuration to the new deployment and event delivery to subscribed internal services resumed. After that, we replayed whatever events could be safely re-emitted, so downstream services could reconcile. ## Follow-up Actions * Enforcement of pre-deployment configuration validations. * Tune Solutions service-side alerting: thresholds for failed installs and uninstalls should fire a High severity alert earlier instead of emitting a low-severity signal. * Messaging service events anomaly detection: Alerts for service on sudden drops in delivery rates and rising failure rates.