Multiple Regions - Agents - Partial Outage

Update timeline

1. identified Mar 18, 2026, 07:52 PM UTC

   We have identified the cause of the disruption impacting Prepare Python environment step for Agents in Multiple Regions and are actively implementing a fix. Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed. Next update: Additional updates will be provided as remediation continues.

2. identified Mar 18, 2026, 08:46 PM UTC

   We are actively working on implementing a fix. Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed. Next update: Additional updates will be provided as remediation continues.

3. resolved Mar 18, 2026, 10:34 PM UTC

   We are actively working on implementing a fix. Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed. Next update: Additional updates will be provided as remediation continues.

4. postmortem Apr 17, 2026, 04:53 PM UTC

   ## **Customer Impact** Between March 16, 2026 12:30 PM and March 18, 2026 at 9:55 pm UTC, a subset of customers experienced failures when running coded agents. Agent execution failed during the "Prepare Python environment" step when the agent's configuration specified a minimum Python version of 3.12 or higher. Customers using UiPath Agents or coded agents configured for Python 3.11 were unaffected. The impact was limited to coded agents in all production regions except Europe, where the affected version had not yet been deployed. A workaround was available — lowering the Python version requirement to 3.11 in the agent's configuration — though this required repackaging and republishing the agent. ## **Root Cause** As part of a security improvement, the Python installation method in the agent runtime environment was updated. The new configuration restricted the package manager's ability to download and install Python versions on demand at runtime. The runtime environment was deployed with only Python 3.11 pre-installed, while Python 3.12 and 3.13 — which are also supported versions — were not included. As a result, coded agents specifying a minimum Python version of 3.12 or higher could not prepare their execution environment and failed to start. The issue originated from a version mismatch within a layered deployment architecture composed of multiple dependent components. During staging validation, the regression was identified and corrected in one component layer. However, during the subsequent promotion cycle, an older version of that layer was inadvertently referenced in the final deployment configuration. As a result, the production environment was deployed without the full set of supported Python versions. ## **Detection** The issue was identified on March 18, 2026 at 7:30 pm UTC after internal stakeholders observed job failures. Following incident initiation by our engineering team, the impact was quickly confirmed to be isolated to Coded Agents, specifically agents requiring Python 3.12 or higher. ## **Response** Our engineering team evaluated reverting the change but determined that doing so would negatively impact other agent types. The team chose a forward fix: rebuilding the runtime environment to include all supported Python versions \(3.11, 3.12, and 3.13\) and redeploying across affected regions. The updated environment was deployed to all affected regions by 9:55 pm UTC on March 18, 2026, and service was fully restored. The incident was formally closed at 10:37 pm UTC. ## **Follow-up** To prevent similar incidents, we are implementing the following improvements: * **Pre-deployment validation:** Automated checks in the deployment pipeline to verify that all supported Python versions are included in the runtime environment before deployment. * **Automated alerting:** Expanded monitoring to detect and alert on failures in the agent environment preparation step. * **Enhanced change review:** Configuration changes affecting agent runtime environments will require compatibility testing across all supported agent types before deployment.