Robovue
Start free
Menu

Automation Anywhere monitoring on every edition, including Community Edition

Each bot reports its own runs to Robovue with two REST Web Services actions. Robovue alerts your team when an automation fails or misses its run, alongside every other platform you use. Email alerts come with every plan, and the Team plan adds Slack, Microsoft Teams and webhooks.

Start free See the three steps
Your botsEach bot reports its own runs

Your automations this morning

Example
  • Supplier onboardingExpected 06:00Missed
  • Purchase order entryFailed at 07:03Failed
  • Claims intakeCompleted at 07:30On time
  • Email to your team · 06:05Supplier onboarding missed a run. Its last run was yesterday at 06:00.
  • Slack on the Team plan, #rpa-alerts · 06:05Missed · Supplier onboarding missed a run.
An example morning: your bots report their runs to Robovue, and your team is alerted when the 06:00 automation never starts.

What Robovue watches

Every run a bot reports becomes a run on the bot’s page, and a schedule on the bot catches the automations that never start.

  • Every run’s outcome. A run shows as Running when it starts. It ends as a success, or as Failed with the bot’s own error message.
  • Automations that do not happen. Give the bot a schedule, and Robovue marks it Missed when its time passes with no job.
  • One bot per Bot ID. Each bot sends its own Bot ID, so use the automation’s name. You can add owners, tags and a credential expiry date.
  • Alerts that do not depend on the Control Room. Robovue sends them itself, so a problem with the Control Room’s own notifications cannot silence them.

Connect it in three steps

You add a report to the start and the end of each bot. The Automation Anywhere page in Robovue gives every action, setting and name to copy.

  1. Copy your address and key

    Start free, then open Automation Anywhere in Connections. Keep the key in the Control Room’s Credential Vault.

  2. Add the two reports to your bot

    A Post method at the top reports the start. Another in the bot’s Finally block reports how it ended, with any error message.

  3. Run the bot once

    The Automation Anywhere page shows the report arrive, or says why it was rejected. Then register the bot and give it a schedule.

ExampleWhat step 3 shows in the app

Before the first run

Nothing has arrived from a bot yet.

This step checks again every 30 seconds.

Once a report has arrived

Connected. Your bot’s last report arrived at 07:30.

What it needs

Any edition
Community, Cloud and On-Premises all work, because each bot sends its own reports. The Control Room needs no API key, so Community Edition can connect.
A device with the Bot Agent
Each report is an HTTPS request from the device that runs the bot. The Control Room itself can stay on a private network.
The Automation Anywhere key
Each bot reads it from the Control Room’s Credential Vault. It can report runs and do nothing else.
Or connect your Control Room
On a paid edition, Robovue can read your Control Room’s job activity every 3 minutes instead, with an API key. This way has not yet been checked against a real Control Room.

Know about the next failed automation first

You need no card and no sales call. Connect your first bot in a few minutes.

Start free See pricing