All templates

Automated Blue Prism Bot Failure Alerts

Every hour, WebRun opens the Blue Prism control room, reviews the process queue for every bot, flags any run that failed or exceptioned, saves a dated log of the failures to Google Drive, and texts the RPA admin through Twilio when more than a handful pile up unresolved.

Deploy this workflow Browse all templates

Runs on WebRun · Strict Lockdown policy

Every hour, day and night WebRunorchestrates each step

Blue Prism check the process queue for failures

Google Drive save the failure log

Twilio text the RPA admin

In short

How do I get alerted when Blue Prism bot runs are failing?

WebRun reviews the Blue Prism process queue every hour, flagging any bot run that failed or exceptioned and saving a dated failure log to Google Drive. When more than 5 failures sit unresolved it texts the RPA admin through Twilio naming the affected processes, so a stuck automation queue gets attention before it backs up further.

Stuck process queues get caught within the hour, not the next audit
A dated failure history builds up in Drive automatically
The admin gets texted only when failures genuinely pile up

Built for RPA administrators · enterprise automation teams · IT operations · process excellence teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

WebRun signs in and gets to work

Opens blueprism.com in a real browser with your saved login - no setup, no API keys.
1
Blue Prism - check the process queue for failures

blueprism.com

WebRun checks the process queue for failures in Blue Prism.
- Open the control room and review the process queue
- Filter to runs that failed or exceptioned
- Capture the process name, bot, and exception reason
Done when Every failed run in the queue is captured.
2
Google Drive - save the failure log

drive.google.com

WebRun saves the failure log to Google Drive.
- Save the failures as a dated log file
- File it in the RPA operations folder
- Keep prior logs for a running history
Done when This run's failure log is saved to Drive.
3
Twilio - text the RPA admin

twilio.com

WebRun texts the RPA admin through Twilio.
- Text the RPA admin when more than 5 failures are sitting unresolved
- Name the affected processes
- Stay quiet when the queue is running clean
Done when The admin is texted only when failures have genuinely piled up.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run

blueprism.com

ScheduleRuns automatically on this cadence

Every hour, day and night

DeliveryHow each run's result reaches you

Failure alert · Twilio

OutputWhat each run produces - A dated failure log saved to Google Drive, with a text to the RPA admin when failures pile up.

Text

Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.

Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST

Typed input ALLOW

Shell command BLOCK

File uploads BLOCK

Runs in a contained environment More on policies

Good to know

Questions, answered

Will it restart or retry a failed bot run?

No. WebRun only reports and logs failures. Restarting or retrying a process stays a manual step for your RPA admin.

What counts as piled up?

More than 5 failed runs sitting unresolved in the queue at once, which usually points to a systemic issue, not a one-off exception.

Does it check every bot and process?

Yes. It reviews the full process queue across every bot in the control room, not just one.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.

Deploy this workflow Talk to us