Questions and answers

What is Robovue?

Robovue watches the bots you already run on UiPath, Automation Anywhere, Power Automate and your own code. It alerts your team when a run fails, or when a bot misses a run on the schedule you give it. Email alerts come with every plan, and the Team plan adds Slack, Microsoft Teams and signed webhooks. Your bots keep running where they are: Robovue never starts, stops or changes them.

How is it different from the alerts my RPA platform already sends?

Each platform’s own alerts cover only its own bots. Robovue shows all your bots in one place, and catches missed runs as well as failed ones. It also keeps each bot’s owners, maintenance windows and credential expiry dates, and on Team, the time the bot saves. Its alerts do not depend on the platform being monitored, so a problem with the platform’s own notifications cannot silence them.

How long does setup take? Do I need to talk to anyone?

Connecting your first bot takes about ten minutes, and you do not need to talk to anyone. You sign up, open Connections in Robovue and connect a platform with your workspace’s credentials. A Verify step then shows your first run arriving.

Do I need a card to start?

No. The Free plan needs no card, and neither does the 14-day Team trial.

Do I have to install anything on my bot machines?

No. UiPath Orchestrator and Power Automate send each run to Robovue themselves. An Automation Anywhere bot reports its own runs with two actions you add to it. Your own code sends signed HTTPS requests, through the .NET or Python SDK or from any language.

How do I check it’s working before I rely on it?

Every connection has a Verify step. It shows your first run arriving, or the exact reason a request was rejected. A log keeps your latest requests from the last 7 days. Your code, Power Automate and Automation Anywhere bots can also send a dry run, which runs every check and stores nothing.

Which platforms does Robovue work with?

UiPath, Automation Anywhere, Power Automate and your own code, in any language. UiPath Orchestrator sends Robovue a webhook. An Automation Anywhere bot reports its own runs on any edition, including Community Edition. A Power Automate flow reports each run itself: a desktop flow with Invoke web service, free on Windows, and a cloud flow with the HTTP action, a Premium connector. Your code sends a signed HTTPS request, or uses the .NET or Python SDK. See UiPath, Automation Anywhere, Power Automate and your code.

Can I monitor Blue Prism, Python or other tools?

Yes, with a signed HTTPS request or one of the SDKs. Each run report carries a short platform label you choose, such as python or blue-prism, so those bots sit alongside all your others. Robovue has no connector made for Blue Prism.

Is there an SDK for .NET or Python?

Yes. For .NET Framework 4.6.2 or later and .NET 6 or later, run dotnet add package Robovue.Sdk (NuGet). For Python 3.9 or later, run pip install robovue-sdk (PyPI). Each SDK signs every request, checks a report before sending it and can send dry runs while you set up. It also retries when the network or Robovue has a problem. Any other language can send the request itself: Robovue shows it in C#, Python, PowerShell and shell, with a signature checker.

What licence are the SDKs under?

MIT, so you can use, change and ship them freely. The code examples in Robovue are under MIT-0, so you can paste them into your own code without keeping any notice. Neither licence ends when a subscription does.

My Automation Anywhere Control Room is on-premises. Will it work?

Yes. Each bot reports its own runs over HTTPS from the device it runs on, so the Control Room can stay on a private network. Robovue can also check a Control Room’s job activity with an API key, but that way has not yet been checked against a real Control Room. It needs a public HTTPS address on port 443, and its checks do not come from a fixed address.

Do I need a Premium licence for Power Automate?

Not for a desktop flow. Power Automate for desktop is free on Windows 10 and 11, and a desktop flow reports its own runs with Invoke web service. That is proven with a real flow. A cloud flow reports with the HTTP action, which is a Premium connector, so the flow’s owner needs a Power Automate Premium licence. Cloud flows have not yet been checked against a real flow.

Can I manage my setup from code?

Yes, most of it. The Management API covers bots and their schedules, days-off calendars, tags, owners, maintenance windows, workspace alert settings, alert channels and run history, using your workspace’s Management API key. Some things can only be changed in Robovue. These include a bot’s name and failure alert threshold, people, billing, the Automation Anywhere connection and deleting the workspace.

What does Robovue alert on?

Robovue alerts when a bot misses a run or a run fails, and again when the bot recovers. A failure can alert on the first one, after several in a row, or when a share of recent runs fail.

Where do alerts go?

By email to the people in your workspace, on every plan. The Team plan adds Slack channels, Microsoft Teams channels or chats, and signed outgoing webhooks. A webhook carries alerts into your own tools, or anything else that accepts an HTTPS request. Every webhook comes from one fixed address, shown in Robovue, so your firewall can allow it. Each person can switch off each kind of alert email for themselves. Robovue has no built-in SMS, paging or other chat app.

Are email alerts included on the Free plan?

Yes. Email alerts are on every plan. Slack, Microsoft Teams and webhook alerts need the Team plan.

Will I get flooded with alerts?

No. Robovue alerts when something changes, not on every run. A bot that misses a run sends one alert, then another when it recovers. A failing bot opens one incident and alerts again only when it recovers. You can raise the failure threshold for the whole workspace or for one noisy bot.

How do schedules work?

Each bot you add says when it runs, in one of three ways. "Runs every" counts from the end of the bot’s last run, from every minute to every 30 days. "At set times" gives the bot up to 10 named schedules, such as "Morning run: weekdays at 08:00", "the last working day of the month" or "every 2 weeks on Friday", each in its own time zone. You can fill one in by pasting a UiPath cron expression or a Power Automate recurrence. "Runs when needed" is for a bot with no schedule: it gets failure alerts and is never Missed.

Each schedule has a grace period of up to 7 days. If a run does not arrive when expected, the bot shows as Late. Once the grace period passes too, it shows as Missed and Robovue alerts. Robovue starts watching a bot once its first run has finished. You can also give a bot a run time limit, and a run that goes on longer marks the bot Missed. A bot that reports without being added has no schedule, so it is never Missed.

My bot only runs on weekdays. Will it show as Missed at the weekend?

No, if you give it a set-time schedule for weekdays. Robovue then expects no run on Saturday or Sunday. For bank holidays and other dates, add a days-off calendar to the schedule. You can type its dates in Robovue, upload them as a CSV file, or start from a ready-made UK or US holiday calendar.

What happens when the clocks change?

A set-time schedule keeps its clock times in its own time zone, so an 08:00 run is still expected at 08:00 after the change. A time the clocks skip is expected just after the gap, or, if you choose, later by the length of the gap (as UiPath and Power Automate run it) or not at all that day. A time that happens twice is expected once. A bot that runs every few hours counts real hours instead.

Can I stop alerts during planned maintenance?

Yes. A maintenance window covers one bot, or every bot with a tag. Alerts wait until the window ends. A bot that is still failing then alerts at that point. A bot that missed a run during the window gets until its first run due after the window, plus its grace period, before Robovue alerts, so a planned outage does not end in a false alarm.

Does Robovue warn me when a bot’s credentials are about to expire?

It flags the bot in Robovue, but does not send an email or channel alert. Record the expiry date of the credential a bot uses, and Robovue flags the bot for review from 30 days before. Once the date has passed, it marks the credential expired.

How quickly does Robovue alert me about a problem?

Within about a minute. Robovue checks for missed and failed runs every minute, and alerts as soon as it finds one. Runs from a connected Automation Anywhere Control Room can take up to 3 more minutes to arrive, because Robovue checks it every 3 minutes.

What do Reports show?

Reports review how your bots did over a period you choose, such as last month, compared with the period before. They show the share of runs that succeeded, failed and missed runs, and why runs failed. A list ranks the bots that need attention, and every bot’s figures download as a CSV file. Reports need the Team plan, and reach back as far as your plan’s run history.

How does Robovue work out time and money saved?

You set the minutes each bot saves per run, and what each run is worth if you want a money figure. Robovue multiplies those by the bot’s successful runs, leaving out runs during maintenance windows. Money is shown in pounds, dollars or euros. The figures are estimates, as good as the values you set, and need the Team plan.

How much does Robovue cost?

Free is £0 for up to 5 bots and 30 days of run history. Team is £29 a month for 25 bots and 90 days of run history. It takes more bots in blocks of 25 at £19 a month, up to 200. Business, with unlimited bots and unlimited run history, is not open to new workspaces yet. Prices are in pounds and include any tax. See pricing for every limit.

Do you charge per person?

No. Every plan includes unlimited people, under fair use, and you pay for bots. Admins invite people and manage billing. Members can add bots and change their settings.

What counts as a bot?

A bot is one process, automation or flow that reports its runs to Robovue. On UiPath, it is one process, whichever robots run it, and runs from Studio’s Run or Debug button are not counted. On Automation Anywhere, it is each Bot ID your bots send, usually one per automation. On Power Automate, it is each bot ID your flows send, usually one per flow. For your code, it is one job your code reports.

What does fair use mean for people?

Every plan includes unlimited people, with fair-use limits on workspace size, invitations and alert emails. The pricing page lists the exact numbers. Running extra workspaces to get round the limits is not allowed, but an agency can keep one workspace for each client, with a separate sign-in for each.

What does Team add over Free?

• 25 bots instead of 5, and more in blocks of 25 up to 200
• 90 days of run history instead of 30
• Slack, Teams and webhook alerts
• Failure screenshots
• Hours and money saved, per bot
• Reports on how your bots did and what they saved

Can I add bots without changing plan?

On Team, yes. Team includes 25 bots, and an Admin can add more on the Billing page in blocks of 25, at £19 a month each. Team holds up to 200 bots. Extra bots start once the workspace is paying, so they are not available during a free trial. A block you remove stops at your next renewal, with no refund or credit. Our terms explain how blocks are charged. For more than 200 bots, talk to us about Business.

How does the free trial work?

Each workspace can try Team free for 14 days, once, with no card, as long as it has never paid. When the trial ends, the workspace goes back to Free and keeps everything it set up. Team features pause, as they do on a downgrade. If you subscribe during the trial, your first charge waits until the day the trial would have ended. You can pay straight away instead, and the whole days you have not used come off your first payment. With less than 49 hours of the trial left, you are charged straight away.

How do I get Business?

Business is not open to new workspaces yet. It adds unlimited bots and unlimited run history. Talk to us about what you need.

What happens if I go over my plan’s bot limit?

A new bot is rejected at the limit, and Admins receive an email about it. If a downgrade leaves you over the limit, every bot keeps alerting for 14 days. After that, only as many bots as the plan includes keep alerting: the ones an Admin picks, or otherwise the ones added first. The rest keep recording runs, and no bot is deleted for being over the limit. Archived bots count toward the limit until an Admin deletes them, and so does any bot that reports runs without being added.

What happens if I downgrade or cancel?

A cancellation takes effect at the end of the period you have paid for, and the workspace moves to Free. Features the smaller plan does not include are paused with their settings kept, and come back if you upgrade. Run history older than the new plan keeps is deleted 14 days later. Fees already paid are not refunded, apart from the exceptions in our terms.

How do I pay, and who sends the invoice?

You pay monthly, in advance. Link, Stripe’s reseller service, takes the payment. It sends your receipts and invoices, handles any VAT and may charge in your local currency. You change plan, update your payment details or cancel in the billing portal, from Billing in Robovue.

Where is my data stored?

In the UK, in AWS’s London region. Some providers, such as Stripe, may process data outside the UK, and those transfers are protected as UK data protection law requires. The subprocessors page lists them all. Alerts you send to your own Slack, Microsoft Teams or webhook fall under your agreement with that provider.

Do you have a data processing agreement?

Yes. The data processing agreement is part of the terms of service, so there is nothing separate to sign. Admins receive 30 days’ notice by email before a new subprocessor is added.

What do my bots send, and how long is it kept?

Whatever your bots report: names, run status and times, error messages and an optional payload, up to 64 KB for each report. On the Team plan, a failed run can also carry a screenshot or log. Run history is kept for 30 days on Free, 90 days on Team and with no limit on Business. Screenshots and logs are kept for 30 days, or 7 or 14 if an Admin chooses. Please do not send special-category personal data or card numbers.

How is my data protected?

It is encrypted in transit (HTTPS only) and at rest, and each workspace can read only its own data. Every request from a bot carries a secret key or a signature, and Admins can rotate keys without breaking running bots. If a breach ever affected your data, we would tell you within 48 hours of finding out.

How do I delete my data?

An Admin can delete a single run from its page, or an archived bot with all its runs. To delete everything, an Admin deletes the workspace from the Account page. That cancels any subscription at once and removes the workspace’s data and everyone’s sign-in. Backups keep a copy for up to 7 days, and application logs, which can include your email address, for 30 days. To ask about your own personal data, email contact@robovue.co.uk.

Can I turn on two-step sign-in?

Yes. Anyone can add an authenticator app from Account in Robovue, and they’re then asked for a code at every sign-in. Each person chooses for themselves, and Robovue does not send codes by text message.

Can I export my run history?

Yes. Your run history downloads as a CSV file of up to 10,000 runs, filtered as you choose, and each run can be downloaded on its own. On the Team plan, Reports download too. The Management API reads runs as well.

Can I use one sign-in for several workspaces?

No. Each sign-in belongs to one workspace. To work in another, use a different email address, or leave your current workspace from Account in Robovue first.

Who runs Robovue?

Robovue is based in England and registered with the Information Commission (the ICO). It is sold to businesses only. The operator’s details are under Who we are in the privacy policy. For help, email contact@robovue.co.uk, or use Send feedback in Robovue.

Is there an uptime guarantee?

No. Plans do not include a service level agreement. Robovue’s live status is on its status page, checked by an outside service.