DRIFTSTACKAPI errors

API error type

Session not ready

HTTP 409 https://errors.driftstack.dev/session-not-ready

What it means

A message reached an agent session whose browser is still starting: the session exists and reads status: "active", but it has not yet reported ready (its ready is still false). The message waited for it — for up to 45 seconds on a streamed response, 20 seconds on a JSON one — and the session was still starting, so nothing ran. The body carries code: "session_not_ready", retryable: true and retry_after_seconds; the Retry-After header carries the same wait.

How to fix it

Send the same message again after retry_after_seconds — the same Idempotency-Key is safe to reuse, because nothing ran. Better, wait for GET /v1/agent-sessions/{id} to read ready: true before sending the first message. A session on a VPN can take longer to become ready. If the session closes while ready is still false, it failed to start, and its closed_reason says why.

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