Skip to content
Destesi Docs

Ask AI

Ask anything about Destesi — setup, products, APIs.

Powered by Claude. Answers may be wrong — always verify against the docs.

Drive troubleshooting

Upload is rejected as too large

Section titled “Upload is rejected as too large”

Drive accepts files up to 5 GiB. A larger file is refused before it finishes uploading. Split or compress the file, or store the original elsewhere and keep a smaller artifact in Drive.

“name_conflict” when creating a folder or uploading

Section titled ““name_conflict” when creating a folder or uploading”

File and folder names are unique (case-insensitive) within their parent folder. A 409 name_conflict means a live item with that name already exists alongside it. Rename one of them, or upload into a different folder.

A file I expected from another product isn’t here

Section titled “A file I expected from another product isn’t here”

Artifacts from Chat, Studio, Text-to-Speech, and Image generation land in their per-product folders (Chat generated, Studio generated, and so on). Check the matching folder first. Video that Studio renders lands in Render generated rather than Studio generated, so check both.

If it’s still missing:

  • Confirm you’re in the right workspace — Drive only shows the active workspace’s files. Switch workspace from the launcher and look again. See workspaces.
  • Confirm the producing product actually finished. An artifact is registered in Drive only once generation completes; a run that failed or is still in progress won’t have written a file yet.

“not_found” for a file or folder I know exists

Section titled ““not_found” for a file or folder I know exists”

Drive returns 404 not_found for anything outside your active workspace — it never reveals that a file belongs to a different workspace. If you’re hitting this:

  • Make sure you’re operating in the workspace that owns the item.
  • If you’re using a personal access token, check the X-Destesi-Workspace header names the correct workspace.

API returns 401 even with a token

Section titled “API returns 401 even with a token”
  • unknown_bearer_scheme — the Authorization header isn’t a recognized token. Drive accepts Bearer drive_… keys and Bearer idn_pat_… personal access tokens; anything else is rejected (and Drive won’t fall back to a cookie when a bearer is present).
  • api_key_invalid — the key isn’t recognized. Re-check you copied the full token; the plaintext is shown only once at creation.
  • api_key_revoked — the key was revoked. Mint a new one in the Drive web app.
  • missing_session / session_invalid — your browser session expired. Sign in again at account.destesi.io.

Can’t create an API key

Section titled “Can’t create an API key”

Creating a key returns 403 cookie_required when the request is authenticated with a bearer token. API keys can only be minted from an interactive browser session — open the Drive web app and create the key there.

Section titled “A signed download link stopped working”

Signed content URLs (the …/content?ws=…&exp=…&sig=… links returned by uploads and downloads) are valid for one hour. After that they return 403 invalid_signature. Request a fresh download link from the file, or re-list the file to get a new signed URL.

A 503 on file operations

Section titled “A 503 on file operations”

A 503 means a backing service was briefly unreachable: store_unavailable when the metadata database can’t be reached, or storage_unavailable when file storage can’t be reached. When only storage is down, folder and API-key operations may still work while file content does not. Retry the operation shortly; if it persists, the backend is down rather than your request being wrong.