Open a profile: the server and the one-device lock

Starting a profile first takes a launch lock on the Browz server. The lock keeps each profile open on one computer at a time, across your team, and it is how access changes and transfers take effect straight away. So a profile opens only while the server can be reached: Browz refuses the launch rather than open it without the server.

1. launch-server-unreachable: the Browz server cannot be reached. Check your connection and try again. Nothing was started.
2. launch-server-error: the server answered but did not confirm the lock. Try again shortly; the message includes what the server said.
3. launch-signed-out: your session has ended. Sign in again, then start the profile.
4. profile-open-on-other-device: the profile is open on the computer named in the message. Stop it there first. If that computer went offline, the lock expires within the number of seconds the message gives.
5. profile-lock-not-held: you asked to attach to a profile that is already running, for example a Start with reuse from a script, but this computer no longer holds its launch lock. Another computer may have taken it, or the server has not confirmed it. Stop the profile and start it again.

While it holds the lock, Browz brings in the browser session the last computer left, so the profile continues where it stopped. If that cannot be restored, the profile still opens with this computer's own copy, and the activity log says so.

The launch banner shows the error code next to the message. Mention it if you contact support.

Team refusals: profile-access-denied and profile-transfer-pending →

Still stuck? Contact support →

Still stuck? Export diagnostics and contact support.