API error type
Profile already in use
HTTP 409 · https://errors.driftstack.dev/profile-in-use
What it means
A session-create carried a profile_id that already has a live (non-terminal) session. A profile can run only one session at a time — two sessions on the same profile would both restore and then overwrite the same saved cookies and logins, losing your data. The body carries active_session_id, the live session you already have running. Sessions without a profile_id are never affected.
How to fix it
End the session named in active_session_id (or wait for it to finish), then launch again. If you need parallel runs, use separate profiles.
Where it appears
In the type field of the RFC 9457 application/problem+json error body, alongside title, status, detail, and an instance correlation id.
Related
- Conflict
· /conflict - Concurrent session limit reached
· /concurrency-limit - Storage quota reached
· /storage-quota-exceeded