Resolved — UiPath Solutions deployment failures (Delayed US, Delayed EU)

Update timeline

1. resolved Aug 03, 2026, 02:11 PM UTC

   Between 03-08-2026 07:47 UTC and 03-08-2026 11:24 UTC, organizations on the Delayed US and Delayed EU update rings were unable to deploy UiPath Solutions. The issue was introduced by a configuration change applied at 07:47 UTC. That change was reverted at 11:24 UTC, which restored Solutions deployment functionality for all affected organizations. We have monitored the affected environments since the revert and confirm the issue is fully mitigated. No customer action is required.

2. postmortem Sep 02, 2026, 02:56 PM UTC

   ## Customer impact Between 07:47 UTC and 11:24 UTC on August 3, 2026, organizations on the Delayed US and Delayed EU update rings were unable to use UiPath Solutions deployment functionality: the Solutions management pages were unavailable and deployment operations could not be performed. Running automations and all other Orchestrator functionality were not affected, and no data was lost. The total customer-impacting duration was approximately 3 hours and 37 minutes. No customer action was required after the fix was applied. ## Root cause As part of routine configuration hygiene, a set of feature-flag definitions that were no longer referenced by the latest Orchestrator release was removed from our centralized configuration system at 07:47 UTC on August 3, 2026. The removal was validated against the latest codebase only. Environments on the Delayed update rings intentionally run an earlier Orchestrator release, and that release still evaluated one of the removed flags to control access to Solutions management functionality. Once its definition was removed, the flag resolved to its default (disabled) value in those environments, which made the Solutions deployment experience unavailable. ## Detection The issue was brought to our attention through a customer report received at 10:15 UTC on August 3, 2026, approximately 2 hours and 28 minutes after the configuration change was applied; no automated alert detected the degradation. The formal incident was opened at 13:43 UTC, after the customer-impacting period had already ended. ## Response Engineering traced the failure to the configuration change and reverted it at 11:24 UTC, which immediately restored UiPath Solutions deployment functionality for all affected organizations. The affected environments were monitored after the revert, and the incident was marked resolved at 14:11 UTC once monitoring confirmed they remained healthy. ## Follow up 1. **Feature-flag evaluation telemetry** — We are adopting runtime usage telemetry for feature flags, so that cleanup decisions are driven by actual evaluation data from every environment and release version, rather than by static code inspection. 2. **Configuration deletion safeguard** — We are adding a safeguard to the centralized configuration platform that detects when a flag definition is still being consumed by any deployed service version and prevents its deletion until usage reaches zero.