Common issues
When connecting the Runner
"Invalid identifier or password."
Check the robot account identifier (or the personal account email) and the password. A robot account's password is shown only once, at creation: if it was lost, a Proton administrator generates a new one with Generate new credential. See Runner account.
"This identifier does not have an active license to connect Runner."
The account needs a Runner only or Full access license in the organization. A Proton administrator assigns the license to the account, under Access & Teams > Username.
"Connection denied: user already connected to server."
The account already has a runner connected on another machine. Each account connects one runner at a time: disconnect the other one or use a different account on this machine.
"You belong to more than one organization. Select which one the runner will join."
Choose the organization in the connection. To switch later, edit the connection in the Runner.
"You no longer belong to this organization." or "This user does not belong to any organization."
The account left the organization or was deactivated in it. Ask a Proton administrator for access or choose another organization.
When running
The run takes a while to start
The first run of a repository on a runner downloads the code and prepares the dependencies (uv or Maven downloads everything the project uses) before the first step, and can take a few minutes. Later runs use the cache. The run log shows which stage it's at.
"uv" or "mvn" is not recognized
The machine doesn't have uv or Maven on the PATH of the user running the runner. Install it (see
Python projects and Java projects) and restart the Runner, which reads the PATH
when it opens.
The runner doesn't recognize the project
The runner recognizes the project by the file at the root of the repository: pom.xml for Java and pytest.ini for
Python. If both are at the root, pom.xml wins. The Proton MCP project check
(check_project) points out this and other issues before running.
The run is refused because the runner is offline
An immediate run on an offline runner is refused. Check the Runner on the machine, choose another runner or a cluster, or schedule the run.
A desktop or SAP GUI automation fails for no clear reason
The Windows session was locked, minimized in a remote desktop, or in use by another user. See Desktop and SAP GUI automations.
"adb not found"
Install Android Platform Tools, put adb on the PATH, and restart the Runner. See Mobile (Android).
The mobile run keeps waiting for the device
Each device handles one run at a time: the run waits for the one using the device to finish. The Runner window shows which run has it.