August 2026 release notes for Action Center in Automation Cloud.

The following changes affect how due status and due time are used to triage actions in the Actions list.

The Sort & Filter panel in the Actions list now includes a Due Status filter, which replaces the previous Timer Status filter. The filter is multi-select, so you can combine statuses — for example, Overdue together with Due soon — to surface the work closest to breaching its service-level agreement (SLA).

On the Pending tab, an action reports one of the following statuses:

On the Completed tab, the list adds a fifth status, Completed in time, for actions completed before their completion timer expired. The panel also adds a Due Time filter (Next hour, Next 24 hours, Next week, or a Custom range of up to 30 days) and a Due Time sort (Soonest Due on Top or Farthest Due on Top).

Each action row displays its due status, color-coded, with a tooltip giving the completion due date and time. Due status, the Due Status filter, and the Due Time sort apply to the task's completion timer only, not the assignment timer. For more information, see Configuring task timer.

Timers configured with Task assigned as the end criteria no longer appear in the Action Center interface. These timers continue to run, and their configured outcome still triggers when they expire — only the display is removed.

The interface now shows completion timers only, meaning timers configured with Task completed as the end criteria. For more information, see Configuring task timer.

The definition of the Due soon status will change in a future release. Until then, an action becomes Due soon once 80% of its completion timer duration has elapsed. After the change, an action becomes Due soon when 24 hours remain on the completion timer, regardless of the timer's total duration.

Completion timers shorter than 24 hours will report Due soon for their entire duration, and will never report Due later.

Correction - August 7, 2026: This feature has been temporarily disabled again for stabilization improvements. We'll announce when we plan to re-enable it.

The Report a technical issue button was first enabled on August 3, 2026, then temporarily disabled on August 4, 2026 while UiPath reviewed customer feedback about how the reported data is handled. It is available again as of August 5, 2026, and is documented here for the first time.

A Report a technical issue button is available in Document Validation and Document Classification actions. Reviewers can report a technical error, a crash, or unexpected screen behavior that blocks their work, attach an anonymized copy of the taxonomy and the extraction or classification result, or temporarily switch to a previous version of the screen. The report does not capture the document or any text values read from it.

For details on what data this button sends and who can access it, see Report a technical issue button.

When a Document Validation action is configured to open in the classic view, the Validation Station now offers to switch to the compact view, and back again at any time. The prompt appears above the document and can be dismissed permanently with Close and don't show again.

The choice is remembered per reviewer, in the browser they made it in, and does not change the action, the document, or the extraction result. Actions configured to open in the compact view are unaffected, and continue to open in that view.

The view an action opens in is set by the DisplayMode property of the Create Document Validation Action activity.