DRIFTSTACKAPI errors

API error type

Device unavailable

HTTP 409 https://errors.driftstack.dev/device-unavailable

What it means

The profile you launched is on a device that is not offered right now: it is on hold until the evidence behind it exists, or still in development. The device picker shows such devices but does not offer them, and GET /v1/archetypes does not list them. The launch was refused before any session existed, so nothing started and no concurrent-session slot was used. The body carries archetype (the profile’s device) and, when there is one, held_reason (the reason for the hold, in one plain sentence).

How to fix it

Launch a profile on a device listed by GET /v1/archetypes. A profile keeps its device, so create one on another device if you need to run now.

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