Uipath Conversational Agent Outage in Europe Region

Final update

## Customer Impact Between 2026-08-06 07:30 UTC and 2026-08-06 07:48 UTC (~18 minutes), some customers in the Europe region experienced intermittent HTTP 500 errors when using their conversational agents. Affected customers may have encountered errors when opening or listing their conversations, or starting new conversations. No data was lost, and the service recovered automatically. ## Root Cause The incident was caused by a temporary disruption in an internal caching component used by the Conversational Agent Service in the Europe region. During the disruption, the caching layer returned unexpected responses, which the service did not handle gracefully. This caused a portion of customer requests to fail instead of completing normally. The caching component stabilized on its own after approximately 18 minutes, and service resumed without manual intervention. ## Detection The issue was detected by automated monitoring, which triggered an alert within minutes of the errors beginning. Additional alerts continued to fire as the condition persisted. ## Response - **07:36 UTC** - Automated alert detected the issue and an incident was created. - **07:48 UTC** - The caching component stab

1. Postmortem · Aug 19, 13:13 UTC
   ## Customer Impact Between 2026-08-06 07:30 UTC and 2026-08-06 07:48 UTC (~18 minutes), some customers in the Europe region experienced intermittent HTTP 500 errors when using their conversational agents. Affected customers may have encountered errors when opening or listing their conversations, or starting new conversations. No data was lost, and the service recovered automatically. ## Root Cause The incident was caused by a temporary disruption in an internal caching component used by the Conversational Agent Service in the Europe region. During the disruption, the caching layer returned unexpected responses, which the service did not handle gracefully. This caused a portion of customer requests to fail instead of completing normally. The caching component stabilized on its own after approximately 18 minutes, and service resumed without manual intervention. ## Detection The issue was detected by automated monitoring, which triggered an alert within minutes of the errors beginning. Additional alerts continued to fire as the condition persisted. ## Response - **07:36 UTC** - Automated alert detected the issue and an incident was created. - **07:48 UTC** - The caching component stabilized and errors stopped. The service recovered without manual intervention. - The engineering team confirmed the recovery and investigated the root cause through application telemetry. ## Follow-Up To prevent similar incidents in the future, we are taking the following steps: - **Improving service
2. Resolved · Aug 6, 07:30 UTC
   On 06/08/2026 between 7:31 AM - 7:47 AM UTC Uipath Conversational Agent had an outage in Europe region. During this time impacted Customers were unable to access their conversations and create new conversations. The issue is resolved now.