Catch Blue Prism bot failures before the queue backs up
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.
- No credit card
- Under $0.01 per run
- Cancel anytime
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.comin 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 How to Automate Google Drive
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 How to Automate Twilio
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.
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
How is each run configured?
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.
Every action is checked against this policy before it runs.
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.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.