All templates
For RPA teams, automation centers of excellence & IT operations

Catch failed UiPath bot runs before they pile up

Every hour, WebRun opens UiPath Orchestrator, checks the job history for runs that faulted or failed since the last check, logs each failed transaction with its process name and error to Google Sheets, and emails an alert through Gmail when a single process has failed more than once in the same hour.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every hour WebRun
1 UiPath check Orchestrator run history for failures
2 Google Sheets log each failed transaction
3 Gmail email an alert for repeat failures
Run a sample
In short

How do I get alerted when a UiPath bot run fails?

Every hour, WebRun checks UiPath Orchestrator for bot runs that failed or faulted, logs each one with its process, step, and error message to Google Sheets, and emails an alert through Gmail when a single process fails more than once in the same hour, so a broken RPA process gets caught the same day, not at the next audit.

  • A broken RPA process gets caught the same day, not at audit time
  • A full failure log builds up automatically in Google Sheets
  • One-off failures stay quiet so alerts stay trustworthy

Built for RPA teams · automation centers of excellence · IT operations · shared services 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.

  1. WebRun signs in and gets to work

    Opens cloud.uipath.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    UiPath - check Orchestrator run history for failures
    uipath.com
    WebRun in UiPath: check Orchestrator run history for failures
    WebRun opens UiPath to check Orchestrator run history for failures.
    • Open UiPath Orchestrator and review the jobs list for the past hour
    • Filter to jobs that ended faulted or failed
    • Capture the process name, the failed step, and the error message for each

    Done when Every job that failed in the past hour is listed with its cause.

  3. 2
    Google Sheets - log each failed transaction
    google.com How to Automate Google Sheets
    WebRun in Google Sheets: log each failed transaction
    WebRun opens Google Sheets to log each failed transaction.
    • Open the bot failure log in Google Sheets
    • Add a row per failed job with its process, step, and error
    • Keep prior hours in place so failure patterns are visible

    Done when This hour's failures are logged alongside the failure history.

  4. 3
    Gmail - email an alert for repeat failures
    gmail.com How to Automate Gmail
    WebRun in Gmail: email an alert for repeat failures
    WebRun opens Gmail to email an alert for repeat failures.
    • Check whether any single process failed more than once this hour
    • Draft and send an alert email through Gmail naming that process and its errors
    • Skip the email when failures are isolated one-offs across different processes

    Done when An alert has gone out only for processes with repeat failures this hour.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
cloud.uipath.com
ScheduleRuns automatically on this cadence
Every hour
DeliveryHow each run's result reaches you
Bot failure alert · Gmail
OutputWhat each run produces - A logged Google Sheets row per failed UiPath job, plus a Gmail alert when one process fails more than once in the same hour.
Alert
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

Does it restart the failed bot run?

No. WebRun only reads the job history and logs what failed. Restarting a job or fixing the underlying process stays with your automation team in UiPath.

Why log every failure but only email on repeats?

A single isolated failure often clears on retry, so it just gets logged. An email goes out once a process fails more than once in an hour, since that usually points to something actually broken.

Can I see failure patterns over time, not just this hour?

Yes. Every hour's failures add rows to the same Google Sheets log, so recurring problem processes are easy to spot over days or weeks.

Put this on autopilot.

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