‘Profile already in use’: its other live session has to end first
You might be here because: “Profile already in use” · “End the profile’s other live session before launching it again” · “it says the profile has a session but I closed the window” · “can’t launch the same profile twice” · “409 profile-in-use” · “profile stuck as running”
Short answer
A profile can run in only one session at a time. Two sessions on the same profile would both save their cookies and logins back at the end and overwrite each other, so the second launch is refused. If you started the profile’s running session, stop it (Sessions tab, or its row in Profiles), then launch again. If a teammate or a script started it, ask them, or wait for it to end.
Check first
- Closing the session window does not always end the session. Look in the Sessions tab for this profile.
- Did you, a teammate, or a script launch it elsewhere? The rule is per account, across every computer and API key.
- Do you just want to get back to the running session? Use Watch/open on its row instead of launching again.
Likely causes and fixes
-
The profile really is running. The server refuses with HTTP 409
profile-in-use, detail “This profile already has a live session (…). End it before launching another — two sessions on the same profile would overwrite each other’s saved cookies and logins.”. The app shows “End the profile’s other live session before launching it again.”. Fix: find the session. If you started it, press Stop, then launch; if someone else did, ask them or wait for it to end. -
The session is still starting or still closing. Any session that is not yet closed counts. Wait a moment, refresh, then retry.
-
A script left it open. Sessions created from code hold the profile until closed. If the script is yours, close the session from the code, or stop it in the app. If it is someone else’s, ask them before you stop it.
If it still fails
If no session shows as running for that profile yet the launch is still refused after a couple of minutes, press Talk to a person in this chat (or open Help) and include the profile name and the session id shown in the message (active_session_id). Nothing about this needs an account or billing action.