RPA in 2026: what's left for recorded robots — and what replaces them

Classic RPA promised the office without copy-paste. In 2026 the pitch has changed vocabulary: the same vendors that sold recorded robots now sell "agentic" automation, and Gartner projects that over 40% of agentic AI projects will be canceled by the end of 2027 — due to escalating costs, unclear business value or inadequate risk controls. Here is what classic RPA still does well, where it breaks, what agentic automation actually adds, and how to decide — with named sources.

What classic RPA still does well

A recorded robot is deterministic: it clicks the same buttons, reads the same fields, and never improvises. For a process with a stable UI, high volume and zero ambiguity — re-keying invoices from one legacy system to another, downloading daily reports, reconciling fixed-format files — that is exactly what you want. Robots don't get bored, don't mistype, and run at 3am. Vendors like UiPath (founded 2005, publicly listed) built an enterprise category on this, and that layer isn't disappearing.

Where recorded robots break

The same determinism is the weakness:

• Any UI change breaks the script. A moved button, a renamed field, a browser update — the robot fails and a human re-records it. Maintenance, not licences, becomes the real cost.
• Exceptions don't route themselves. A missing field, a new supplier, a partial payment: anything outside the recorded happy path either halts the process or piles up in a review queue nobody staffed.
• Long-running work doesn't fit. Processes that span days, people and systems (onboarding, claims, credit approval) need orchestration, not a macro.

That maintenance burden is measurable: in LangChain's State of AI Agents survey of ~2,200 practitioners, roughly 30% report difficulty maintaining agents in production, and 13.5% of teams running agents in production reported a security breach. Automation without an operator plan is a liability, whatever runs it.

What "agentic" actually adds

Agentic automation inverts the workflow: instead of recording clicks, you describe the process in plain language and an agent executes it with the right tools, guardrails and a full audit trail — reasoning about the goal when a screen changes or an edge case appears. Human-in-the-loop stops being a bolted-on exception queue and becomes a designed step: edge cases route to your team with context.

Honest caveat, straight from Gartner: most agentic projects today are early experiments driven by hype, and the market is full of "agent washing" — assistants and chatbots rebranded as agents. Gartner counts only ~130 genuinely agentic vendors out of thousands claiming the label. The label tells you nothing; the guardrails, audit trail and operating model tell you everything.

Even UiPath sells agentic now

The clearest signal of the shift is the incumbent itself. UiPath's current platform pages market Autopilot, "the natural-language AI built into the UiPath Platform", that turns plain-language descriptions into workflows, agents and tests, with every action passing through its AI Trust Layer for audit trails and policy controls. In June 2026 it launched Maestro Case — orchestration where "human review and escalation can be built into the process for exceptions" — and in August 2026 Maestro Flow, developer-first orchestration for coding agents. Its own framing: agents think, robots do, people lead. Classic robots aren't gone — they're becoming one worker inside an agent-orchestrated fleet.

The cost question, with numbers

UiPath no longer publishes list prices — enterprise pricing is quote-based, and the old fixed plans have given way to consumption units (RUs, AI Units, API calls). Market compilations from 2026 (AIMultiple, EPC Group) still put the reference point at ~$420 per attended robot per month and ~$1,380 per unattended robot per month — treat them as orders of magnitude, not quotes. The budget that surprises teams, though, is the same in both models: building and maintaining the automations. Gartner's "escalating costs" and LangChain's 30% maintenance figure describe the same phenomenon — automation is a permanent operating cost, not a project.

How to decide

• Keep recorded robots for stable, high-volume, rule-fixed screens where the UI rarely changes.
• Go agentic where processes change often, cross systems, or drown in exceptions — and demand the three things that separate agents from chatbots: guardrails, human-in-the-loop, audit trail.
• Decide by who operates it. If nobody owns monitoring, patching and exception review in production, both models fail — Gartner's cancellation number is mostly an operating-model failure.

Decide with the full picture

We break the decision down from three angles: Paperclip vs UiPath compares agentic RPA with classic RPA head-to-head, UiPath alternatives surveys the market when you're outgrowing classic robots, and what is agentic RPA explains the category from zero. Paperclip is our take: workflows written in prose, shipped as agents with guardrails and a full audit trail — and HostAgentes hosts them on managed EU infrastructure from $3.99/mo.

The short answer

Classic RPA still owns stable, high-volume screens; it loses wherever the UI moves or exceptions pile up. Agentic automation — plain-language workflows, reasoning agents, human-in-the-loop, audit trails — is where UiPath itself is steering with Autopilot and Maestro. But Gartner projects over 40% of agentic projects canceled by 2027 because vendors washed the label and buyers skipped the operating model. Choose by stability of the process, guardrails, and who operates it in production — not by the word on the box.