UiPath experienced a notice incident on July 1, 2026 affecting Agentic Orchestration, lasting 2h 38m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jul 01, 2026, 05:29 PM UTC
This issue is causing degraded performance impacting maestro instances and team is currently investigating the issue. Impact: Workflows may experience slowness or get stuck.
- monitoring Jul 01, 2026, 06:46 PM UTC
The immediate issue has been mitigated. However, because this specific failure mode develops gradually over time, we have additional monitoring in place and collecting more diagnostic data to prevent a recurrence.
- resolved Jul 01, 2026, 08:07 PM UTC
The issue remains quiet and has not resurfaced. We are implementing our active monitoring and rapid-response guardrails in place while the engineering team continues investigating the root cause.
- postmortem Jul 30, 2026, 10:36 AM UTC
## **Customer Impact** Between **July 1, 2026 at 17:18 UTC** and **July 1, 2026 at 20:07 UTC**, a subset of customers experienced degraded performance in **Maestro**. During this period, some workflows executed more slowly than expected or became stuck, which may have delayed automation execution. The issue affected **Maestro instances in the EU region**. Service was fully restored after mitigation was applied, and workflow processing returned to normal. ## **Root Cause** The incident was caused by memory exhaustion in the Maestro workflow processing service. A small number of workflow executions encountered errors that caused them to repeatedly retry instead of stopping. As these executions remained active, they consumed increasing worker resources until some worker instances exhausted available memory and restarted, resulting in degraded workflow processing. The immediate mitigation increased the memory available to the affected worker service, restoring normal operation. Engineering is implementing additional safeguards to ensure workflows encountering non-recoverable failures stop after a defined number of retries and cannot consume unbounded service resources. ## **Detection** The issue was detected through automated monitoring at **17:18 UTC** on **July 1, 2026**, which immediately triggered incident creation. Follow-up investigation and log analysis confirmed that the affected workflow worker service was experiencing out-of-memory errors. ## **Response** Following detection, engineering began investigating the degraded workflow processing and identified memory exhaustion within the workflow worker service as the source of the issue. Customers were notified through the public status page while the investigation was in progress. Engineering increased the memory allocation for affected worker services in the EU region, restoring normal service behavior. Affected workflow instances were reset where necessary to allow processing to resume. Following a period of monitoring that confirmed stable operation and no recurrence of the issue, the incident was resolved. ## **Follow-Up** To help prevent similar incidents, we are implementing the following improvements: 1. **Workflow retry safeguards:** Implement product improvements to ensure workflows that encounter non-recoverable failures stop after a defined number of retries and cannot consume unbounded worker resources. 2. **Increase worker capacity:** Increase memory allocation for the Maestro workflow worker service in both the EU and U.S. regions to reduce the likelihood of recurrence from the same memory exhaustion pattern. 3. **Enhanced monitoring:** Maintain additional monitoring and diagnostic data collection for this failure mode so that gradually developing memory pressure can be identified earlier.