Runs
Run the code project manually, follow the run history, watch live logs and stop a run.
Runs
A run is one pass of the robot on a device, using the deployment that is ready on it. The Runs tab gathers the project's history across every device and trigger.
Running manually
- Click Run in the project header.
- Choose the Environment: Preview or Production. Projects that receive code by .zip only have Production.
- Choose the Device. Roberty preselects the best candidate in the environment.
- Confirm with Run.
When you choose Production, the run affects the real environment — it is the same run as an API call.
A device can only be used if it is active, online, runs Windows and has a ready deployment. If the chosen environment has no device, link one in the settings, Devices tab. See Devices.
Manual runs take no arguments: the arguments file only exists in webhook and evaluation runs. See Arguments and result.
The Run button is disabled when the project has no linked device or is turned off. While a manual run is in progress, the header shows Follow, which opens the live run, and Stop.
Errors when starting
| Message | Cause |
|---|---|
| This device has no deploy ready to run. | The device doesn't have a finished deployment yet. See Deployments. |
| Device not authorized for this project. | The device is not linked to the project. |
Run list
The Runs tab lists the runs from every device and trigger, 20 runs per page. Search by device, environment, trigger, status or ID, and use the refresh button to reload the list.
The In progress block shows the runs happening right now, regardless of page or search.
| Status | Meaning |
|---|---|
| Pending | The run was created and is waiting for the device. |
| Running | The robot is running on the device. |
| Success | The process exited with code 0. |
| Failed | The process exited with another code or could not finish. |
| Trigger | Source |
|---|---|
| Manual | The project's Run button. |
| Schedule | A schedule on a Production device. |
| Webhook | A call to the API. |
Evaluations also create runs, with the evaluation trigger.
Run details
Click a run to open its details: trigger, environment, device, start and end.
- Queued — if the device is busy, the run shows as "Queued for {device}": the device picks the run up as soon as it is free.
- Logs — the robot's
stdoutandstderr, live while the run is in progress. Use Copy logs to copy the content and Show log timestamps to display the time of each line. If you see "Log unavailable: the runner could not upload the log.", the device could not send that run's log. - Error screenshot — when a run fails and the device captures the screen, the screenshot shows in the details and can be downloaded. The link expires: if the screenshot doesn't load, close and reopen the panel to generate a new one.
Stopping a run
To stop a run in progress, use Stop in the project header, or Stop in the list or in the details. A confirmation warns that the run on the device will be stopped immediately.
When the user stops the run, the exception entry point is not run.
Turned-off project
While the project is turned off, runs from the Studio and the API are blocked, and the top of the project shows the Project turned off notice with a Turn project on shortcut. The option is in Settings, General tab.
See also
- API and webhook — trigger runs from external systems, with arguments and a response.
- Run Code project — run the project from an RPA robot.
- Preparing the project — exit code and logs.