{% extends "_layout.html" %} {% set title = "Session ended" %} {% set status = "401 Unauthorized" %} {% set description = "The session is over. reason says why. Re-authenticate; never refresh." %} {% block main %}

The session behind your token is over, and no refresh will revive it.

What to do

  1. Sign in again (sc-config remote configure).
  2. Do not refresh: the refresh token belongs to the same ended session.
  3. On reason: "reused", reuse detection ended the session: somebody else spent a refresh token of yours. Your credentials were used elsewhere. Rotate this machine’s key with sc-config remote rotate-key — the machine enrols again as a new device — and then sign in.

Formerly session-revoked and session-expired. They are one type now, with reason saying which.

The body

{
  "type":     "https://sc.example.com/server-errors/session-ended",
  "title":    "Session ended",
  "status":   401,
  "detail":   "...",
  "instance": "/v1/jobs/01J9...",
  "reason":   "expired",  // REQUIRED on this type
  "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
Member
reasonREQUIRED revoked — the session was revoked, or its refresh token was reused; deactivated — the account was switched off; expired — it aged out, and nothing went wrong.
trace_idoptional The request’s W3C trace id. Quote it in a support request.

detail is prose and may be reworded at any time. Branch on type, and read the members above for the specifics — never parse detail.

Where it comes from

any authenticated endpoint
POST /v1/auth/token A refresh against an ended session.
{% include "_help.html" %}

What this is not

invalid-token is refreshed. This one never is.

{% endblock %}