Skip to main content
Go to the Studio
Robot settings

Run history

Run history

The history is the complete record of every time a robot has run — by hand or on a schedule. It shows the status of each run, how long it took, and gives you logs and screenshots to diagnose the failures.

Reaching the history​

From the Designer​

  1. Open the robot's Designer.
  2. In the side menu, click History.

From Roberty Studio​

  1. Open the Robots section in the Studio's side menu.
  2. Find the robot.
  3. Click Settings (⚙️) and choose Full run history.

What the history shows​

The history screen is a table of every recorded run. Each row gives you:

ColumnWhat it is
ModeWhether the run was Manual (started by hand, by webhook or by WhatsApp) or Scheduled
Run dateWhen it started and ended, with the total duration (e.g. 2h 15m 30s)
DeviceWhich machine ran the robot (shown for runs on other devices)
Status✅ Success, ❌ Failure or 🔄 Running
Relative timeHow long ago the run was (e.g. "2 hours ago")

Filtering the history​

Use the filters at the top to find specific runs:

  • Device — filter by which machine ran the robot
  • Period — pick a date range (31 days maximum per query)

Click Search to apply them.

Reading the output logs​

For every finished run you can read the logs it produced — system messages, the errors it hit, and anything the robot recorded itself.

  1. Find the run in the table.
  2. Click Output logs.

The logs walk through what happened step by step — useful for pinning down where the robot failed, and why.

Viewing the error screenshot​

When a run on another device fails, Roberty automatically captures a screenshot at the moment of the error. It is particularly useful for seeing what was on screen when the problem happened.

  1. Find the failed run in the table.
  2. Click Screenshot (available only for failed remote runs).

Runs on different devices​

If the history contains runs from more than one device, the screen shows two tabs:

  • On this device — runs that happened locally (on the machine you are on)
  • On other devices — runs that happened remotely, with the device column visible

Diagnosing a failure​

Pair the history with snapshots. If a run that worked yesterday fails today, compare the date of the problem with the snapshots you have. Something in the flow or the environment may have changed.

Logs are your best resource. Before investigating anything else, open the failed run's logs. Most of the time the error message names exactly which action and which field caused the problem.

Filter by period. If you suspect the problem started after a particular date, filter the history to that period to find the first failed run.

Next​