UiPath Status

Postmortem: ## Customer Impact

Customers using Action Center in the Australia, Canada and subset of users from Europe regions were unable to click on or edit fields in Advanced Form Tasks. Because the form could not be edited with the mouse, affected users could not fill in, save or complete these tasks through the normal workflow. Fields could still be reached with the keyboard Tab key, so users were not fully blocked. All other task types, and Form Tasks using the standard form layouts, were not affected.

Impact began after an Action Center update was deployed to these regions on the evening of September 21, 2026, and ended on September 22, 2026 at approximately 07:30 UTC, when the fix was deployed to all affected regions. Total duration was approximately 12 hours.

Root Cause

The Action Center update included a new feature that lets customers save a task directly from the task view when Action Center tasks are embedded inside Case apps. To make the save option visible in that embedded view, a styling (CSS) change was made that places the save control on a higher display layer than the task details.

The feature logic itself was only enabled for embedded tasks, but the styling change could not be limited in the same way and was applied to every task view. Advanced Form Tasks render their form inside a separate, isolated container so that they can support additional custom controls. For these forms, the new display layer sat on top of the form, creating an invisible overlay that captured mouse clicks and prevented users from interacting with the form fields.

The change was tested manually and through automated end-to-end tests across all task types before release. However, the Form Tasks used in testing all used the default, standard form layout. Advanced Form Tasks, which developers must explicitly enable in UiPath Studio, were not part of the test coverage, so the issue was not detected before the update reached production.

Detection

The issue was detected through customer reports. The first report arrived as a high-severity support ticket on September 22, 2026 at 00:30 UTC, which paged the on-call engineer, followed by a second report through a support help request at 01:30 UTC.

The update was deployed outside business hours, and the post-deployment automated validation passed in each region because it did not cover Advanced Form Tasks. As tasks still loaded and no errors were generated, there was no alert or monitoring signal for this issue, and it only became visible once users started working on these tasks during business hours.

Response

The on-call engineer engaged immediately after being paged and brought in the engineers who owned the change. While the fix was being prepared, affected customers were given a workaround to use the keyboard Tab key to move between and edit form fields, which was confirmed as working. Mitigation began at 00:30 UTC and the issue was fully resolved at 07:30 UTC on September 22, 2026.

Timeline (September 22, 2026, UTC):

• 00:30 – First customer report received; on-call engineer paged and engaged immediately.
• 01:30 – Second customer report received through support.
• 02:20 – Root cause identified and reproduced in a test environment.
• 03:30 – Fix validated in a test environment.
• 05:30 – Fix validated in the pre-production environment.
• 07:30 – Fix deployed and validated in all affected production regions (Community, Australia and Canada). Issue resolved.

Follow-Up

Short-term

• The styling change has been corrected so that it applies only to tasks embedded in Case apps and no longer affects the standard task view or Advanced Form Tasks.
• We are adding Advanced Form Tasks (form layout version 3) to our manual and automated end-to-end test suites for Action Center.

Long-term

• We will include Advanced Form Tasks in the automated validation that runs after every Action Center deployment, in every region, so that this type of issue is caught before it can reach customers.
• We will review our test coverage to make sure every supported form layout version is exercised when changes are made to the task view.

Resolved: The fix has been applied and validated, and the service is operating normally

Monitoring: The fix has been successfully applied, and the service is currently under monitoring.

Users should now be able to scroll and edit Form Tasks in Action Center when using Advanced Forms. We will continue monitoring the service to confirm that the issue remains resolved.

Identified: We have identified an issue affecting Advanced Forms in Action Center for users in the Canada and Australia regions and subset of users in european union region. A hotfix deployment is currently in progress.

Impact: Users may be unable to scroll or edit Form Tasks as expected when using Advanced Forms.

Workaround: Use the Tab key to navigate through the form and make edits instead of clicking or scrolling.

Next update: Our focus is on completing and validating the hotfix deployment and restoring full functionality and share and update quickly as possible

Postmortem: ## Customer Impact

Customers using Action Center in the Australia, Canada and subset of users from Europe regions were unable to click on or edit fields in Advanced Form Tasks. Because the form could not be edited with the mouse, affected users could not fill in, save or complete these tasks through the normal workflow. Fields could still be reached with the keyboard Tab key, so users were not fully blocked. All other task types, and Form Tasks using the standard form layouts, were not affected.

Impact began after an Action Center update was deployed to these regions on the evening of September 21, 2026, and ended on September 22, 2026 at approximately 07:30 UTC, when the fix was deployed to all affected regions. Total duration was approximately 12 hours.

Root Cause

The Action Center update included a new feature that lets customers save a task directly from the task view when Action Center tasks are embedded inside Case apps. To make the save option visible in that embedded view, a styling (CSS) change was made that places the save control on a higher display layer than the task details.

The feature logic itself was only enabled for embedded tasks, but the styling change could not be limited in the same way and was applied to every task view. Advanced Form Tasks render their form inside a separate, isolated container so that they can support additional custom controls. For these forms, the new display layer sat on top of the form, creating an invisible overlay that captured mouse clicks and prevented users from interacting with the form fields.

The change was tested manually and through automated end-to-end tests across all task types before release. However, the Form Tasks used in testing all used the default, standard form layout. Advanced Form Tasks, which developers must explicitly enable in UiPath Studio, were not part of the test coverage, so the issue was not detected before the update reached production.

Detection

The issue was detected through customer reports. The first report arrived as a high-severity support ticket on September 22, 2026 at 00:30 UTC, which paged the on-call engineer, followed by a second report through a support help request at 01:30 UTC.

The update was deployed outside business hours, and the post-deployment automated validation passed in each region because it did not cover Advanced Form Tasks. As tasks still loaded and no errors were generated, there was no alert or monitoring signal for this issue, and it only became visible once users started working on these tasks during business hours.

Response

The on-call engineer engaged immediately after being paged and brought in the engineers who owned the change. While the fix was being prepared, affected customers were given a workaround to use the keyboard Tab key to move between and edit form fields, which was confirmed as working. Mitigation began at 00:30 UTC and the issue was fully resolved at 07:30 UTC on September 22, 2026.

Timeline (September 22, 2026, UTC):

• 00:30 – First customer report received; on-call engineer paged and engaged immediately.
• 01:30 – Second customer report received through support.
• 02:20 – Root cause identified and reproduced in a test environment.
• 03:30 – Fix validated in a test environment.
• 05:30 – Fix validated in the pre-production environment.
• 07:30 – Fix deployed and validated in all affected production regions (Community, Australia and Canada). Issue resolved.

Follow-Up

Short-term

• The styling change has been corrected so that it applies only to tasks embedded in Case apps and no longer affects the standard task view or Advanced Form Tasks.
• We are adding Advanced Form Tasks (form layout version 3) to our manual and automated end-to-end test suites for Action Center.

Long-term

• We will include Advanced Form Tasks in the automated validation that runs after every Action Center deployment, in every region, so that this type of issue is caught before it can reach customers.
• We will review our test coverage to make sure every supported form layout version is exercised when changes are made to the task view.

Resolved: The fix has been applied and validated, and the service is operating normally

Monitoring: The fix has been successfully applied, and the service is currently under monitoring.

Users should now be able to scroll and edit Form Tasks in Action Center when using Advanced Forms. We will continue monitoring the service to confirm that the issue remains resolved.

Identified: We have identified an issue affecting Advanced Forms in Action Center for users in the Canada and Australia regions and subset of users in european union region. A hotfix deployment is currently in progress.

Impact: Users may be unable to scroll or edit Form Tasks as expected when using Advanced Forms.

Workaround: Use the Tab key to navigate through the form and make edits instead of clicking or scrolling.

Next update: Our focus is on completing and validating the hotfix deployment and restoring full functionality and share and update quickly as possible