Not configured

What it means

Something this request depends on is not set up or not reachable right now.

Common causes

• The keys that verify sign-in tokens could not be loaded.
• Rate limiting is unavailable, so the API refuses instead of running without limits.
• The feature is not turned on in this environment.

What to do

Wait for the seconds in Retry-After, then retry. If it lasts, check the status page.

Retry: safe after a pause. Back off between attempts, and reuse the same Idempotency-Key for a write.

This response also carries Retry-After, the number of seconds to wait before you try again.

Over MCP, the same failure is a tool result with isError: true, the code not_configured and retryable: true.

Example

A response body for this problem. The detail and instance vary with the request.

{
  "type": "https://api.tobie.team/problems/not_configured",
  "title": "Not configured",
  "status": 503,
  "detail": "Rate limiting is unavailable",
  "code": "not_configured",
  "instance": "/v1/tasks",
  "requestId": "01JC0S7Z5F3X9QK2M4N6P8R0TV"
}