Why does a profile say it is in use?

Distinguish a local browser process from the latest run record shown in team or operations views. Current versions no longer use a cross-device runtime lease: a session on another device does not block launch here. The client still prevents duplicate launches of the same profile on this device.

Identify which case applies

1. Still running on this device: Check the taskbar and other desktops for an existing window. Use that window, or close it normally before relaunching.
2. Running on another device or by a teammate: This is a coordination and data-version issue, not a wait for runtime permission to expire. Agree on who should continue editing to avoid two different copies.
3. An old run record remains visible: An unexpected exit, power loss, or network interruption may prevent the last stop report from arriving. A team or operations record does not prove that a remote process is still running and does not block launch.

Troubleshoot in order

1. Check for a local browser process or a launch, close, or deletion operation still in progress. Let that local operation finish before retrying.
2. Before switching devices, save work on the original device, close the profile normally, and confirm that any changes you need have synced.
3. Sign in on the target device with access to the profile, refresh the list, and launch. Launch still requires a connection to retrieve configuration; this is not a fully offline launch mode.
4. If a message still asks you to wait for another device to release the profile, check for an old client and contact support to confirm version compatibility. Do not keep waiting for a removed lease to expire.

Refreshing only reads state. Clearing a run record does not close a browser on another device. Network problems no longer force an already started browser to close because it cannot renew a lease, but sign-in, configuration retrieval, and sync requests can still fail.

Multiple devices do not imply automatic data merging

The same profile can run on multiple devices. Uploads check the cloud version on which the local data was based. A conflicting old copy does not silently overwrite committed data, and local changes are retained. MaskPilot does not automatically merge two browser directories.

To continue with recent changes, confirm that the original device allows uploads, close normally, and check the sync result. A stopped status alone does not prove that an upload succeeded. Preserve the copies on each device when versions conflict; see sync and recover profile data.

Keep local process protection intact

Local browser directories still have process protection. Do not delete, copy, or replace a profile directory or lock files while its browser is active, and do not repeatedly force-quit the client to dismiss a message. This is separate from the removed server-side runtime lease.

If launch still fails after the local process has ended, record the client version, profile name, current operator, original message, shutdown method, and approximate time before contacting support. Keep website sign-in details, proxy passwords, and other credentials out of screenshots and logs.

After changing a fingerprint, proxy, or extension, continue with the profile settings checklist and verify the result after one complete restart.