Skip to main content

storage_not_configured

HTTP 409 · code: "storage_not_configured" · type: https://docs.formfeed.dev/errors/storage-not-configured

The request needs the workspace's own bucket (bring your own storage), but the workspace has no storage connection. On a render, field is storage.key. Nothing was rendered or charged.

Example​

{
  "type": "https://docs.formfeed.dev/errors/storage-not-configured",
  "title": "Storage not configured",
  "status": 409,
  "detail": "storage.key names an object in the workspace's own bucket, but workspace fennlor has no storage connection; connect one in Settings or leave storage.key out",
  "code": "storage_not_configured",
  "field": "storage.key",
  "request_id": "req_4b7c1e9a2f3d4c5b8a6e7f9012"
}

Common causes​

  • A render, a batch item or a PDF tool request with storage.key in a workspace without a connection. For a batch, detail starts with the first such item (Item 3: …), and nothing is queued.
  • A request built for one workspace, sent with the key of another, for example a test workspace that never got a connection.
  • The connection was removed with Disconnect on the Your own storage card.
  • Testing the connection or redelivering copies in the app in a workspace without a connection.

How to fix it​

  • Connect a bucket: an owner or admin does that in the app under Settings, on the Your own storage card (Pro plan and above). See Bring your own storage.
  • Or leave storage.key out. Without a connection nothing is copied, and the render works as usual; storage: false is accepted with or without one.

Retry?​

Only once the workspace has a connection, or without storage.key. Send that request with a new Idempotency-Key or without one: a 4xx answer is stored under its key for 24 hours, so the old key returns this problem again. See retrying.