At 3:17 AM, the on-call engineer’s phone buzzes. An unattended RPA bot has halted in the middle of an invoice reconciliation job and left an orphaned file. The team has to jump in, debug, and re-run. They have done this dozens of times in the last three months. The bot is stable for weeks, then a UI change in the ERP forces a rebuild of the selectors. The process breaks again. The engineer wakes up again. This is the hidden cost of staying on traditional RPA.
Why RPA breaks at night
Unattended RPA bots rely on brittle selectors and object IDs. When a UI refresh, a layout shift, or a new app version arrives, the bot no longer finds the target element and halts. Industry surveys show that 30, 40 percent of RPA maintenance is spent rebuilding bots after UI or system changes. A single change in the ERP can trigger weeks of rework across multiple bots. The cost is not just engineering hours. It is the operational risk of missed SLAs, delayed reconciliation, and unplanned on-call interruptions.
What changes with computer use agents
- Survives UI changes: Agents see the screen and react to where things actually are, not where selectors say they should be.
- No brittle selectors: There is no binding to xpaths or object IDs, so layout shifts or dynamic classes do not stop the agent.
- Recovers from exceptions: When an unexpected state appears, the agent reads the error, decides the next step, and continues instead of halting.
- Follows SOPs as written: A plain‑English standard operating procedure is already almost a prompt. Agents read it and act, with no flowchart bot to build and babysit.
- Works on legacy and Citrix: Because agents move the mouse and type, they can run on virtualized desktops, legacy apps, and environments where RPA struggles.
The one line a VP of automation should remember: Computer use agents see what you see, follow SOPs as written, and recover from errors instead of halting.
How to move without the risk
You do not need to rip and replace everything at once. Start with a high‑pain process that is exception‑heavy, has frequent UI changes, and lives in a mix of modern and legacy apps. Pick a process that already has a written SOP. Run a pilot with a computer use agent side‑by‑side with the current bot. Measure the impact on uptime, exception rate, and on‑call volume. If the agent handles the process more reliably and frees up engineering time, expand to other similar workloads. Keep traditional RPA for high‑volume, stable, backend tasks where you need deterministic throughput. The goal is to reduce the number of processes that wake the on‑call engineer at 3:00 AM.
The durable way forward
The 3 AM pager is a symptom of brittle automation. Computer use agents do not need brittle selectors. They do not halt on the first unexpected state. They can follow SOPs without a flowchart bot. They can run across any app, including legacy systems and virtualized environments. This shifts your on‑call burden from debugging broken bots to managing a resilient digital workforce.
If your team is still waking up to broken RPA bots, it’s time to consider a more durable automation model. Talk to the Coasty team and book a demo to see how computer use agents can reduce exception‑driven on‑call incidents: https://cal.com/coasty/15min
Want to see this in action?
View Case Studies