UiPath incident
Robot allocation changes not reflected in Orchestrator
UiPath experienced a minor incident on May 26, 2026 affecting Orchestrator and Orchestrator and 1 more component, lasting 21m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 26, 2026, 01:30 PM UTC
We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.
- monitoring May 26, 2026, 01:46 PM UTC
The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.
- resolved May 26, 2026, 01:51 PM UTC
The issue has been fully resolved and service is back to operational.