Remote and fleet operation

Run and watch your bots from the web – pair a machine, start or stop a run remotely, grab a screenshot, keep bots armed for unattended work, and read their health banners.

Help CentreOrchestration

You don't have to sit at each machine to operate your bots. Once a bot is paired to your workspace, you can run, watch and manage it from the web – one bot or a whole fleet. This article is aimed at the people who keep automations running day to day.

1. Pair a bot

Install the Automize bot on a machine and pair it to your workspace (see Working with the RPA Bot for setup). Once paired, the bot appears in your workspace and can be selected when you run a process, grouped into a pool, and controlled remotely.

2. Control a bot remotely

From the process map's Run panel you can drive a paired bot without touching it:

  • Play – start a run on the chosen bot.
  • Stop – halt whatever it's doing.
  • Screenshot – capture what's on the bot's screen right now, to see how a run is progressing.

3. Unattended (armed) bots

A bot can be left armed so it runs work on its own when a trigger fires – no one needs to press Play. Pressing Play with no specific process selected puts the bot in this listening state; it stays armed across runs until someone presses Stop. For the trigger types and how arming works, see Triggers and webhooks.

4. Health banners

Each bot reports its health so you can spot trouble before it causes failed runs. Watch for banners such as:

  • Environment degraded – something on the machine isn't right (for example a dependency or resource problem); runs may be unreliable until it's resolved.
  • Connector authorisation expired – a saved connection the bot relies on needs re-authorising before it can be used again.

For a fleet view of how your bots and their work are doing, use the bot and pool widgets on the dashboard.

Related articles

See it working on your own data

Everything documented here ships with the platform – try the document tools free, or go live in 7 days.