Drıftstack docs
Docs

‘This feature is not available on this deployment’ (503)

You might be here because: “This feature is not available on this deployment” · “this feature isn’t available here” · “The service is temporarily unavailable. Try again shortly.” · “503 feature-unavailable” · “Status stream at capacity; retry shortly” · “cookies pane says unavailable” · “the recipe library is not available” · “why does this button do nothing on my server” · “avatar upload not available” · “ai_provider_unavailable” · “The AI service is temporarily unavailable”

Short answer

A 503 of type feature-unavailable means the thing you asked for is switched off where this server runs — an optional feature that was not set up for this deployment — not that the service is down. Retrying does not change it. One case is different: a session create refused with code: "dispatch_no_live_node" means no machine could take a new session just then. It carries retryable: true and a Retry-After header, nothing was created, so send the same request again after the wait. Another is an AI message answered with code: "ai_provider_unavailable": Driftstack’s included AI is temporarily unavailable, nothing ran, and it is not switched off. Wait the retry_after_seconds (also the Retry-After header, unless the turn was streamed), then send the message again with a new idempotency key if you sent one (do not drop the header). On the hosted service, tell support what you pressed; on a self-hosted server, it is the server’s own configuration.

Check first

  • Which surface said it? The desktop app folds this 503 into “The service is temporarily unavailable. Try again shortly.”, so from the app alone you cannot tell a switched-off feature from an outage; a session pane shows the more precise “this feature isn’t available here”.
  • Does everything else work? One action failing while the rest works is this; nothing working is an outage — see the 5xx page.
  • Cloud or self-hosted? On your own server the feature is yours to switch on.

Likely causes and fixes

  1. A session pane: cookies, a proxy switch, history. The server answers those panes with “This feature is not available on this deployment.” when the part of the platform that serves them is not enabled, and the pane shows “this feature isn’t available here”. The request log has its own sentence, “Network logging is not available on this deployment.” Fix: none from your side on cloud; a person can say whether it is expected.
  2. Profile picture upload. Avatar uploads need storage a deployment may not have. Skip the picture.
  3. An AI message. With code: "ai_provider_unavailable" (retry_after_seconds in the body; also a Retry-After header unless the turn was streamed) Driftstack’s included AI is temporarily unavailable: nothing ran, and steps sent without the AI still work. Wait that many seconds, then send the message again with a new idempotency key — the key you sent keeps this answer — and do not drop the key. A turn on your own Anthropic key never gets this answer. Without that code, on a message sent with an idempotency key, this deployment cannot record keys, so the turn did not run; sending the same key again fails the same way, and the same message without the key runs. A 503 on Stop with stop_unconfirmed: true is also worth calling again.
  4. The public status stream. “Status stream at capacity; retry shortly.” is the same type with a 30-second wait: 10 connections per address and 500 in total. Wait the advertised time; a client that keeps reconnecting will loop.
  5. Self-hosted server. The feature is not configured on your server. Write to [email protected] with the feature name; we tell you which setting turns it on.

If it still fails

Press Talk to a person in this chat (or open Help) and include what you pressed, the exact sentence, the time, and — from the API — the response type and detail. On cloud a person can say whether the feature is expected to be on. Nothing here needs a plan change: a plan limit is a different answer, a 403 whose sentence names the plan.