# Reducing Failures in a UiPath Bot Fleet

> TechSupport Team supported ProcessWorks’ fleet of 340 UiPath bots. Over five months, client UiPath records show the bot failure rate falling from 19% to 2.4%. Manual exception work fell from 120 to 22 hours per week.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/case-studies/uipath-bot-failure-application-support/
- Updated: 2026-11-16

Client: ProcessWorks · AI/ML & Data · UK RPA services provider (80 staff)

## Client and engagement facts

- **Client:** ProcessWorks
- **Industry:** AI/ML & Data
- **Business context:** UK RPA services provider (80 staff)
- **Delivery model:** Automation support
- **Application:** RPA bot fleet for enterprise clients
- **Supplied geography:** UK
- **Company size in source:** 80 staff

## Application stack and tools

### Application stack

- UiPath
- Python
- SQL Server
- Azure

### Tools used

- UiPath monitoring
- Jira
- Azure DevOps

Related services: [Application support](https://techsupport-team.com/services/application-support/)

## Why Support Was Needed

The original alerts showed that a bot had failed. Engineers had to reproduce each failure to learn the cause. The new diagnostics captured evidence when the failure happened.

## Technical Work

- Added screenshots to every bot failure.
- Built pre-flight checks for common UI changes (buttons, fields, page layouts).
- Documented the top 20 failure signatures with resolution steps.

## Representative Incident

A customer changed its login page without advance notice. The team documented the failure and added a process for customers to flag UI changes that affect a bot.

## Results and how they were measured

Table: Reported results and their measurement scope

| Metric | Baseline | Result | Units | Measurement window | Source and scope |
| --- | --- | --- | --- | --- | --- |
| Bot failure | 19% | 2.4% | % | 5 months | Client UiPath |
| Manual exceptions | 120 h/wk | 22 h/wk | h/wk | 5 months | Client Jira |
| Run-time SLA | 91% | 99.4% | % | 5 months | Client Azure DevOps |

## Evidence and Limitations

The five-month comparison excludes one customer-side UI change. The team tracked failures in UiPath, manual exceptions in Jira and the run-time SLA in Azure DevOps.

## Customer Change Notifications

The engagement used a change-notification agreement to define when customer-side UI changes entered scope.

## Scope a Similar Engagement

Describe the bots that fail most often, their third-party dependencies and how changes are reported. [Request a support plan](https://techsupport-team.com/contact/) or explore [application support](https://techsupport-team.com/services/application-support/).

## Related pages

- [Application support](https://techsupport-team.com/services/application-support/): The related service for this engagement.

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
