Partial Degradation of Integration Service Event Triggers in the Australia Region

Update timeline

1. resolved Mar 13, 2026, 11:44 AM UTC

   Between 2026-03-13 08:00 UTC and 2026-03-13 11:00 UTC, the Integration Service event triggers experienced partial degradation due to connectivity issues with the database. There was no data loss during this period. however, event delivery would have been delayed.

2. postmortem Mar 20, 2026, 04:31 PM UTC

   ## _Customer Impact_ Between March 13, 2026 at 11:38 am UTC and March 13, 2026 at 11:47 am UTC, a subset of customers in the Australia region may have experienced a partial degradation of event triggers. During this period, automated workflows that rely on event-based triggers may have failed to start as expected, resulting in delays or missed executions for some scheduled or real-time automation tasks. The impact was limited to customers using event-driven automation features in the Australia region. Other regions and core platform functionality remained fully operational throughout the incident. The disruption lasted for approximately nine minutes. ## _Root Cause_ As part of a routine infrastructure maintenance activity, configuration of a database was updated. While the update was successfully applied to one part of the service infrastructure, it was not propagated to a second part due to a gap in the manual deployment process. As a result, that portion of the service continued attempting to connect using an outdated configuration, causing connectivity failures that led to the degradation of Event Triggers for customers in Australia. ## _Detection_ The issue was detected automatically through UiPath internal monitoring and alerting systems, which identified anomalous behavior in the Event Triggers service and triggered alerts. A contributing factor was that the deployment process for this maintenance activity relied on manual steps, which introduced the risk of incomplete propagation across all parts of the service infrastructure. ## _Response_ The following steps were taken to investigate, mitigate, and resolve the issue: * **Detection** — Automated monitoring identified the degradation and an incident was immediately declared. * **Investigation** — The on-call engineering team began diagnosing the issue and quickly identified the root cause as a configuration mismatch introduced during the planned maintenance activity. * **Mitigation** — The affected portion of the service infrastructure was updated with the correct configuration and restarted, restoring full connectivity. * **Resolution** — The Event Triggers service was confirmed to be fully operational within approximately 9 minutes of the incident being declared. ## _Follow-Up_ UiPath is committed to preventing this class of issue from recurring. The following improvements are planned: * **Short-term:** A review of routine maintenance activities will be conducted to confirm that configuration updates have been fully and consistently applied across all components of affected services. * **Long-term — Automated deployment validation:** Configuration changes made during maintenance activities will be automatically propagated and validated across all service components, eliminating reliance on manual steps. * **Long-term — Configuration drift detection:** Monitoring will be enhanced to detect and alert on configuration mismatches across service components before they result in customer impact. * **Long-term — Improved deployment process:** Deployment procedures for maintenance activities will be updated to include explicit validation checkpoints ensuring all service components have received and acknowledged configuration updates before the activity is considered complete.