Automated Automation Anywhere Failure Alerts
Every hour, WebRun opens the Automation Anywhere Control Room, checks bot runs that failed since the last check, exports the failure details with the bot name and error to a dated report in Google Drive, and posts an alert to Slack when the same bot has failed more than once in the same hour.
How do I get alerted when an Automation Anywhere bot run fails?
Every hour, WebRun checks the Automation Anywhere Control Room for bot runs that failed, exports the failure details to a dated report in Google Drive, and posts a Slack alert when the same bot fails more than once in the same hour. This catches a broken RPA bot the same day instead of at the next manual review.
- A broken bot gets caught the same day, not at the next manual review
- A full dated failure history builds up automatically in Drive
- One-off failures stay quiet so Slack alerts stay trustworthy
Built for RPA teams · automation centers of excellence · IT operations · shared services teams
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
automationanywhere.comin a real browser with your saved login - no setup, no API keys. -
1
Automation Anywhere - check Control Room run history for failures
- Open the Control Room and review the activity feed for the past hour
- Filter to bot runs that ended in a failure
- Capture the bot name, the device it ran on, and the error message
Done when Every bot run that failed in the past hour is listed with its cause.
-
2
Google Drive - export the failure report
drive.google.com
WebRun opens Google Drive to export the failure report. - Open the bot failure reports folder in Google Drive
- Save this hour's failures as a new dated report
- Keep prior hours in place so recurring bots are visible
Done when This hour's failure report is saved to Drive.
-
3
Slack - alert on repeat failures
slack.com
WebRun opens Slack to alert on repeat failures. - Check whether any single bot failed more than once this hour
- Post an alert to the automation channel naming that bot and its errors
- Skip the alert when failures are isolated one-offs across different bots
Done when An alert has gone out only for bots with repeat failures this hour.
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
Does it restart the failed bot?
No. WebRun only reads the Control Room activity and reports what failed. Restarting a bot or fixing its underlying task stays with your automation team.
Why log every failure but only alert on repeats?
A single isolated failure often clears on the next scheduled run, so it just gets logged. A Slack alert goes out once a bot fails more than once in an hour, since that usually points to something actually broken.
Can I see which bots fail most over time?
Yes. Every hour's failures are saved as a dated report in Google Drive, so a recurring problem bot is easy to spot across days.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.