A practical migration note for teams that previously relied on UiPath Unassisted Task Mining for discovery of repetitive desktop work. This is a capability-migration guide, not a one-click data-transfer guide.
UiPath removed Unassisted Task Mining from Automation Cloud on 1 December 2025, and states that Unassisted Task Mining projects were deleted and are no longer available from that date. The change does not mean UiPath stopped task mining altogether: its current Task Mining product remains available, but it is designed around capturing and comparing variations of a known task.
UiPath described Unassisted Task Mining as collecting employee desktop data — screenshots and action logs from clicks and keystrokes — and using machine learning to identify repeated tasks with automation potential. It could analyze recorded day-to-day activity and surface task candidates without requiring the team to define the task first. Current Task Mining, formerly called Assisted Task Mining, is used when the task is already known: users record or build traces of that task, compare variations, merge them into a fuller view, and export documentation or automation assets.
The 1 December 2025 date applies to Unassisted Task Mining in Automation Cloud. Automation Suite followed a separate path: UiPath lists the Task Mining service for removal with Automation Suite 2025.10, and states that after upgrading to 2025.10 customers can no longer select the Task Mining service or access their projects.
UiPath says the retirement is part of a broader process-discovery direction: unifying system data, human activity, unstructured communications and robot data into a single view, while making integration between Task Mining and Process Mining a primary investment area. That matters because the migration question is not simply which product name replaces Unassisted Task Mining. It is which evidence and decisions your team still needs.
Former users need to identify which parts of the old discovery capability mattered to their operating model.
Why it matters. You do not necessarily need to recreate the old UiPath interface feature for feature. You need to re-establish the evidence and decisions that the old capability supported.
| If your need is… | Practical path to evaluate |
|---|---|
| You already know the task and want to capture its variants | Current UiPath Task Mining is a direct option to evaluate. UiPath positions it for known tasks, recorded as multiple traces and merged for comparison. |
| You need end-to-end visibility from enterprise-system event data | UiPath Process Mining or another process-mining platform may be the better fit, depending on the systems and event data available. |
| You need process documentation or redesign from existing knowledge | Cartographer, a specialized profile within UiPath Delegate, is an option to evaluate. Cartographer is currently in Public Preview and is designed for business analysts to document AS-IS and TO-BE processes from sources such as transcripts, SOPs and recordings. |
| You relied on Unassisted Task Mining to discover repetitive work from day-to-day desktop activity | Evaluate a task and process-discovery approach that can observe work over time and preserve the operational context you actually need. |
| You no longer need the capability | Doing nothing is a valid option. Preserve any exported historical evidence you still have, and avoid replacing a capability that no longer supports a current business decision. |
Inventory any CSV exports, process maps, task candidates, screenshots, documentation and downstream automation assets retained before removal. Treat a surviving CSV export as evidence and a hypothesis list for validation — not as a direct migration payload that recreates the former project.
If users can already name the task and reproduce it deliberately, guided trace capture may be sufficient. If the requirement is to discover repetitive work that is not already documented, evaluate for that capability explicitly.
Decide whether you need isolated task traces or evidence across applications, interruptions, task switching, handoffs and elapsed time. Do not assume every task-mining approach produces the same level of context.
Current UiPath Task Mining uses a desktop Recorder client for captured traces. UiPath currently documents a maximum of 100 traces per Task Mining project and 500 actions per trace. For VDI, UiPath requires persistent VDI and documents known limitations: virtual-environment capture is not fully supported, VMs are captured only as screenshots without metadata, and concurrent VDI is not supported. If these conditions matter in your environment, make them selection criteria from the start.
Clarify whether the replacement must connect desktop activity to a claim, order, account, case or other business identifier. This determines whether screen-level task evidence is enough, or whether you need broader case and process reconstruction.
Use one representative process and compare the outputs you actually need: task discovery, variants, elapsed time, business context, documentation, deployment effort and the decisions the evidence supports.
The replacement should preserve the business evidence and decisions you still need — not necessarily reproduce the old UiPath experience feature for feature.
No. UiPath removed Unassisted Task Mining from Automation Cloud on 1 December 2025. Current UiPath Task Mining remains available and is positioned for capturing and comparing variations of a known task.
UiPath states that Unassisted Task Mining projects were deleted and are no longer available starting 1 December 2025. Organizations that exported results before removal should preserve those offline copies as part of the migration evidence base.
Not necessarily. UiPath positions current Task Mining, formerly Assisted Task Mining, for known tasks and their variations, while Unassisted Task Mining was used to discover repetitive work from collected desktop activity. The right replacement depends on the capability your team actually needs now.
If your former UiPath Unassisted Task Mining use case depended on discovering how work actually happens — not only recording a predefined task — Stereologic is one option to evaluate.
Stereologic observes work as it is really performed across web, desktop, legacy and office applications, with non-intrusive, no-install desktop-recording software and no Administrator-level endpoint access, and without integrating source systems first. It reconstructs cases, handoffs, variants, interruptions and workarounds, while Deep Task Mining™ adds business detail inside applications so teams can explain delay, rework and lost capacity. Compare your former use case, required outputs and deployment constraints against what Stereologic provides.
Last verified 20 September 2026. UiPath documentation changes; we re-check these sources periodically. All product names and trademarks are the property of their respective owners. Reference to them here is for identification and comparison only and does not imply any affiliation or endorsement.
Bring the use case Unassisted Task Mining was serving and the decisions it supported. We will be straight about whether Stereologic fits it, and what measuring that work would require.