Drıftstack docs
Docs

‘This session has ended and can no longer be used’ (410)

You might be here because: “This session has ended and can no longer be used” · “Session destroyed” · “This session has been destroyed and cannot be used” · “410 session-destroyed” · “my script gets 410 on a session” · “the session I was using is gone” · “why does it say the session ended” · “can I restart the same session”

Short answer

The session you sent that action to is over — it was stopped, timed out, or ended on our side — and a session cannot be brought back. The API answers HTTP 410 session-destroyed, detail “This session has been destroyed and cannot be used.”; the desktop app shows “This session has ended and can no longer be used.”. Launch the profile again to get a new session and send the action there.

Check first

  • Open the Sessions tab. If the session is listed as ended or closed, the 410 is expected.
  • Are you, or a script, still holding an old session id? A new launch gets a new id; anything that reuses the old one gets 410.
  • Did a teammate, another computer, or a program stop it? Stop applies across the whole account.

Likely causes and fixes

  1. The session ended normally. It was closed after inactivity, reached its time limit, was stopped, or was closed from code — and every later action to that id is refused with 410. The “Session ended” overlay’s recap line says which. Fix: launch the profile again; the new session has a new id.

  2. Your program kept a stale id. A 410 is not one of the SDKs’ retryable classes, so isRetryable returns false and the built-in retry does not repeat it. Fix: on 410, create a new session and carry on there rather than retrying the old one.

  3. It ended on our side. If nothing you did ended it, the recap line under “Session ended” names the cause. Launch again; if it repeats, see the page about the connection we run.

  4. 410 or 404? “The requested item was not found” (404) means the id was not found at all; 410 means it existed and is now over. A 404 usually means a mistyped id or one that belongs to a workspace you cannot see.

If it still fails

If the Sessions tab shows the session as running yet every action to it answers 410, press Talk to a person in this chat (or open Help) and include the session id, the profile name, the exact sentence and the time. Nothing here needs an account or billing action.