Major incident

UiPath: US - Maestro - HITL task creation failures within Maestros with HITL task SLA timers configured

Affected: Agentic Orchestration

Current status of UiPath: Partial outage — live UiPath status

Timeline

1. Oct 7, 2026, 21:34 UTC
   investigating
   We are investigating reports of an outage impacting HITL task creation failures for Maestro in US. Impact: Users may be unable to create HITL tasks. Next update: Our teams are working to understand the cause and scope and will share updates as available.
2. Oct 7, 2026, 22:16 UTC
   identified
   We have identified the cause for an outage impacting HITL task creation for Maestro in US and are working to mitigate the issue. Impact: Users may be unable to create HITL tasks. Next update: Our teams are working to mitigate the issue and will share updates as available.
3. Oct 7, 2026, 23:26 UTC
   identified
   We have identified the cause for an outage impacting HITL task creation for Maestro in US and are working to mitigate the issue. Impact: Users may be unable to create HITL tasks. Next update: Our teams are working to mitigate the issue and will share updates as available.
4. Oct 8, 2026, 00:29 UTC
   identified
   We have identified the cause for an outage impacting HITL task creation for Maestro in US and are working to mitigate the issue. Impact: Users may be unable to create HITL tasks. Next update: Our teams are working to mitigate the issue and will share updates as available.
5. Oct 8, 2026, 01:30 UTC
   identified
   We have identified the cause for an outage impacting HITL task creation for Maestro in US and are working to mitigate the issue. Impact: Users may be unable to create HITL tasks. Next update: Our teams are working to mitigate the issue and will share updates as available.
6. Oct 8, 2026, 02:29 UTC
   monitoring
   We are rolling out fix for an outage impacting HITL task creation for Maestros with HITL task SLA timers configured in US and are working to mitigate the issue. Impact: Users may be unable to create HITL tasks within Maestros with HITL task SLA timers configured. Next update: Our teams are working to mitigate the issue and will share updates as available.
7. Oct 8, 2026, 03:28 UTC
   monitoring
   We are rolling out fix for an outage impacting HITL task creation for Maestros with HITL task SLA timers configured in US and are working to mitigate the issue. Impact: Users may be unable to create HITL tasks within Maestros with HITL task SLA timers configured. Next update: Our teams are working to mitigate the issue and will share updates as available.
8. Oct 8, 2026, 04:29 UTC
   resolved
   The fix for the issue impacting HITL task creation for Maestro with HITL task SLA timers configured in US has been fully rolled out. HITL task creation has returned to normal.
9. Oct 26, 2026, 03:16 UTC
   postmortem
   ## Customer impact On 2026-10-05 between 9.30 PM UTC - 2026-10-07 3.30 AM UTC, Maestro BPMN and Case customers using HITL nodes with a configured Task Timer saw failures of their debug and production instances at the HITL stage, with 4xx . About 30 such instances across customers across US and Europe were identified, that were blocked with no workaround. ## Root cause Configuring a task SLA requires an object including the start and end criteria, the timer of the SLA, and the outcome on SLA breach. Customers configure that on the Maestro designer on the HITL node. The outcome was mistakenly kept non-mandatory on the design surface, even though an SLA configuration without an outcome isn't persisted and doesn't make business sense. The Action Center backend team had added a validation to throw a bad request (400) in case of a non null SLA object with a missing outcome. This ended up impacting customers who had added the Start/End criteria on the node but not configured an outcome. Instances that were previously running failed with 400s, and were unable to resume ## Detection A customer reported the issue to Maestro Engineering SME, who raised it internally with the team. The Maestro team investigated this failure, and observed an increasing number of failures for USI, and a few other tenants via logs, leading them to engage the Action Center team. ## Response The Maestro team received report of the issue from the customer via Email, and they did some initial investigation and identified a potential regression, following which, the Action Center SME was engaged, the issue reproduced on lower environments, a rollback of the feature applied and tested, and rolled out to all impacted regions. It was resolved with all instances being internally retried and resuming. ## Follow up 1. Add validation for this scenario across all cross service codebase surfaces to ensure human review 2. Add required monitoring and integration tests in place to detect this issue faster

Updates as published by UiPath (original).