Glossary

Terms

Term	What it is
Environment	The set of variables for a place where the automation runs (addresses, users, passwords), such as Staging or Production. See Environments.
Automation	A sequence of components that tests or performs a process. See Automations.
Cycle	A round of runs of an automation group, such as a sprint or a release of the system.
Business area	An area of the organization that is responsible for processes, such as Finance. See People and Business areas.
Cluster	A set of runners that share the runs among themselves. See Runners and clusters.
Component	A reusable automation step, with the same name in Proton and in the code. See Components.
Robot account	An account made for Proton Runner and for integrations: it connects the Runner and generates tokens, but doesn't access the portal. See Users.
Correlation ID	The unique identifier of a run, which travels with everything the run touches (the Proton log, the runner log, and the systems it calls). Use it to find the run from another system's log.
Dataset	A version of the automation, with the steps and the parameter values. See Datasets.
Team	A group of people. Teams give access to private automations. See Teams.
Evidence	A screenshot, video, or file that the automation sends during the run.
Run	One execution of a dataset on a runner, with the status, the log, the evidence, and the result of each step.
Automation group	The datasets that run together, in the Automation Center, organized into cycles. A group is either for testing (Quality) or for operations (RPA).
License (seat)	The right of a person or robot account to use Proton in an organization: Full access or Runner only. See Licenses.
Batch	The runs triggered together, all at once or by a scheduled run.
Exception	A robot from an operation group that failed, didn't run, or got stuck, in the Operation queue.
Organization	The company in Proton, with its own data, users, and plan.
Parameter	A piece of data that the component receives (input, in_) or returns (output, out_). See Parameters.
General parameter	A value shared across the whole organization.
Profile	The set of permissions a person has in the organization. See Profiles and permissions.
Person	Someone who is responsible for a process or takes part in it, even without using Proton.
Process	A business process that automations serve, in a tree of macroprocesses and subprocesses. See Process map.
Recurring run	A run that repeats on its own: every N minutes or hours, every day, every week, or every month.
Team rule	Who can see a private automation: the people in its teams and the Admin profile. See Teams.
Git repository	Where the automation code lives (GitHub, GitLab, or Bitbucket). See Systems and repositories.
Requirement	A Jira issue (story or epic) linked to an automation or a dataset. See Jira.
Runner	The machine that runs the automations, with Proton Runner. See Environment Setup.
System	What is automated (a portal, an API, SAP), linked to the repository that holds its code.
Data Table	An organization table, with columns and rows, that automations read and write. See Data Tables.
Tag	A label for classifying and filtering automations and datasets. See Tags.
Test Plan	The Xray or Zephyr test plan. It can become an automation group and receive the run results. See Xray and Zephyr.
Dataset variable	A value shared between the steps of a dataset.

Run status

Statuses are shown in English, as is standard across the industry.

Status	What it means
No Run	The dataset hasn't run in this cycle yet. It also marks the steps that never got to run.
Scheduled	Scheduled for a future time.
Submitted	Sent to the runner.
Waiting	The runner received it and is about to start.
Queued	In the runner's queue, waiting its turn.
Loading	The runner is preparing the project: downloading the code and the dependencies.
Running	The steps are running.
Passed	Finished without failures.
Failed	Finished with a failure.
Stopped	Stopped before finishing, by a person or by the runner.
Cancelled	Never got to run: the runner didn't receive the run.

In the Automation Center, the counters group Pending (Submitted, Waiting, and Loading) and Aborted (Stopped and Cancelled).

End reason

Along with the final status, the run details show why the run ended:

Reason	When
Passed	The run finished without failures.
Business failure	A business rule didn't let the run continue, such as a record that already exists. Retrying gives the same result.
Technical failure	An element that didn't appear, a system that was down, or an exception in the code. This is the default reason for a failure.
Environment failure	The environment didn't let the run happen, such as a runner that couldn't prepare the project.
Stopped	The run was stopped before finishing, with the name of who stopped it.
Didn't reach the runner	The runner didn't receive the run.
Runner lost	The runner went offline with the run in progress, and nothing moved for 15 minutes. The run becomes Failed.