Customer Impact

Between 2026-03-09 12:40 UTC and 2026-03-11 06:05 UTC, customers using UiPath Maestro in the enterprise ring experienced failures when running workflows that included download file activities—specifically those configured with connectors such as Outlook's download email Attachment. Affected automations would fail at the file download step, preventing the workflow from completing successfully.

Root Cause

A code change was deployed to Maestro to support a new file download capability requested by an internal team. This change inadvertently introduced a gap in how certain activity configurations were handled, causing download file activities for specific connectors to fail at runtime. The issue was not caught during testing because the affected configurations were not covered by existing automated test cases. Once the root cause was identified, a targeted fix was developed and deployed to restore normal behaviour.

Detection

The issue was detected through internal reports. No automated alerts were fired because the failures produced 400 HTTP errors, and Maestro's monitoring is configured to alert only on 500-level errors—which typically indicate server-side problems rather than client configuration issues. The absence of customer-reported complaints and the resemblance of the failures to common user misconfiguration errors caused the team to initially deprioritize the investigation.

Response

A dedicated incident bridge was created to coordinate the response, and the engineering team identified the root cause. A fix was validated and deployed to all affected environments and production regions by 2026-03-11 06:15 UTC, fully restoring service.

Follow-Up

In the short term, the immediate fix restored the correct behavior for the affected download file activities. As for longer-term improvements, the team is committed to:

1. Expanding automated test coverage to include additional download file activity configurations that were previously not covered.
2. Move all handling of Integration Service activity configurations into the shared integration library that Maestro uses, so that Maestro is no longer affected by configuration changes in those activities.
3. Reinforcing the validation process for patches that touch activity configuration handling before promoting them to production.